Sharing information in a multi-tenant database system

• US 10,558,685 B2
• Filed: 03/14/2016
• Issued: 02/11/2020
• Est. Priority Date: 01/23/2009
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Kuruganti, Aditya S., Doshi, Kedar, Bhatt, Chaitanya, Moxley, William
• Primary Examiner(s): Hoang, Son T
• Application Number:
  US15/069,236
• Publication Number:
  US 20160306866A1
• Time in Patent Office: 1,429 Days
• Field of Search: None
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Data related to a product is received from a first subscriber and stored into a first section of the on-demand database reserved for the first subscriber. The first subscriber then communicates a request to share the product data with one or more second subscribers. Once the first subscriber receives an acceptance from the one or more second subscribers, the product data is stored in a second section of the on-demand database reserved for the second subscriber. Changes made to the data associated with the product are synchronized between the two subscribers.

Claims

1. A method, comprising:

maintaining, by a multi-tenant database system, first data in a first section of the multi-tenant database system reserved for a first tenant comprising at least a group of users and second data in a second section of the multi-tenant database system reserved for a second tenant comprising at least a different group of users, wherein the first data includes a first object, wherein the second tenant does not have access to the first object via the multi-tenant database system, and wherein the multi-tenant database system is remotely located from the groups of users associated with the first and second tenants;

in response to receiving, from the first tenant, a request to send a connection request to establish a connection with the second tenant, the multi-tenant database system sending the connection request to the second tenant, wherein the connection request specifies one or more data fields of the first object to be shared;

in response to receiving an acceptance of the connection request from the second tenant, establishing the connection between the first tenant and the second tenant;

creating, by the multi-tenant database system, a second object in the second section of the multi-tenant database system; and

responsive to a change made to the specified one or more data fields of the first object in the first section, updating, by the multi-tenant database system, one or more data fields of the second object stored in the second section.

2. The method of claim 1, further comprising:

synchronizing, by the multi-tenant database system, a change made to the second object in the second section by updating the first object stored in the first section.

3. The method of claim 1, further comprising:

receiving, at the multi-tenant database system and from the first tenant, customization information, wherein the multi-tenant database system customizes the connection request using the customization information.

4. The method of claim 3, wherein the customization information includes a selected data field of the first object, and wherein changes made to the first object are made via the selected data field.

5. The method of claim 1, wherein the creating the second object includes:

comparing a first data field of the first object to the one or more data fields of the second object; and

based on the comparing, mapping the first data field to a corresponding second data field of the second object without further user input.

6. The method of claim 5, wherein at least a portion of the first data corresponds to the first data field, and wherein at least a portion of the second data corresponds to the corresponding second data field.

7. The method of claim 5, wherein the first data field and the corresponding second data field correspond to a name associated with the first object and the second object.

8. The method of claim 1, wherein the second object is a copy of the first object.

9. The method of claim 1, wherein the first object includes one or more pointers to the second object stored in the second section of the multi-tenant database system.

10. A non-transitory computer-readable medium having computer instructions stored thereon that are executable by a multi-tenant database system to cause operations comprising:

maintaining first data in a first section of the multi-tenant database system reserved for a first tenant comprising at least a group of users and second data in a second section of the multi-tenant database system reserved for a second tenant comprising at least a different group of users, wherein the first data includes a first object, wherein the second tenant does not have access to the first object via the multi-tenant database system, and wherein the multi-tenant database system is remotely located from the groups of users associated with the first and second tenants;

in response to receiving, from the first tenant, a request to send a connection request to establish a connection with the second tenant, the multi-tenant database system sending the connection request to the second tenant, wherein the connection request specifies one or more data fields of the first object to be shared;

in response to receiving an acceptance of the connection request from the second tenant, establishing the connection between the first tenant and the second tenant;

creating a second object in the second section of the multi-tenant database system; and

responsive to a change made to the specified one or more data fields of the first object in the first section, updating one or more data fields of the second object stored in the second section.

11. The non-transitory computer-readable medium of claim 10, wherein the operations further comprise:

storing first privilege information associated with the first tenant, wherein the first privilege information indicates one or more actions that the first tenant is authorized to take,

wherein the sending the connection request is further in response to the multi-tenant database system determining that the first tenant is authorized to send the connection request according to the first privilege information.

12. The non-transitory computer-readable medium of claim 10, wherein the connection request is customized with information specific to an entity associated with the first tenant.

13. The non-transitory computer-readable medium of claim 10, wherein the connection request indicates a plurality of fields associated with the first object that the first tenant has selected to share with the second tenant.

14. The non-transitory computer-readable medium of claim 13, wherein the plurality of fields are associated with the second object, and wherein an update to the second object via one of the plurality of fields synchronizes to the first object.

15. A multi-tenant database system comprising:

a hardware processor; and

a memory coupled to the processor, wherein the memory has computer instructions stored thereon that are executable by the multi-tenant database system to cause operations comprising;

storing first data related to a first object in a first section of the multi-tenant database system, wherein the first section is reserved for a first tenant of the multi-tenant database system, wherein the first tenant comprises at least a group of users;

storing second data in a second section of the multi-tenant database system, wherein the second section is reserved for a second tenant of the multi-tenant database system, wherein the second tenant comprises at least a different group of users, wherein the second tenant does not have access to the first object stored in the first section of the multi-tenant database system, and wherein the multi-tenant database system is remotely located from the groups of users associated with the first and second tenants;

in response to receiving, from the first tenant, a request to send a connection request to the second tenant of the multi-tenant database system, sending the connection request to the second tenant, wherein the connection request specifies one or more data fields of the first object to be shared;

in response to receiving an acceptance of the connection request from the second tenant, establishing a connection between the first tenant and the second tenant;

creating a second object in the second section of the multi-tenant database system; and

responsive to a change made to the specified one or more data fields of the first object in the first section, updating one or more data fields of the second object stored in the second section.

16. The multi-tenant database system of claim 15, wherein the first object is a product object and wherein the first data includes one or more of the following data items:

stock keeping unit (SKU) number, price, description.

17. The multi-tenant database system of claim 15, wherein the operations further comprise:

storing connection request rules associated with the second tenant in the second section, wherein the connection request rules at least indicate how to respond to the received connection request.

18. The multi-tenant database system of claim 17, wherein the connection request rules indicate that a connection request received from a particular tenant will be accepted by default.

19. The multi-tenant database system of claim 15, wherein the operations further comprise:

receiving, from the first tenant, an indication that the first tenant has selected a third object to share with the second tenant.

20. The multi-tenant database system of claim 19, wherein the operations further comprise:

automatically creating a fourth object in the second section, wherein the creating the fourth object establishes a connection between the third object and the fourth object.