Processing offline updates to records of a database system

Patent metadata

Field	Value
Publication number	US-10915519-B2
Application number	US-201615261606-A
Country	US
Kind code	B2
Filing date	Sep 9, 2016
Priority date	Sep 9, 2016
Publication date	Feb 9, 2021
Grant date	Feb 9, 2021

Abstract

Disclosed are examples of systems, apparatus, methods, and computer program products for processing offline updates to records of a database system. In some implementations, a first update to a record is processed, and the record is modified according to a first action and first data of the first update. A second update to the record from a device with an offline status is processed. It can be determined that the second update and the first update are associated with a same portion of the record. It can be determined that the second timestamp is prior to the first timestamp. A notification can be provided to the device. The record can be modified according to a second action and second data of the second update.

First claim

What is claimed is:

1. A system comprising:
a database system implemented using a server system, the database system configurable to cause:
obtaining a first update to a first one of a plurality of records stored in a database, the first update received from a first device, the first update comprising first data, a first action, and a first timestamp;
modifying the first record according to the first action and the first data;
obtaining a second update to the first record and to a second record, the second update received from a second device different from the first device, the second update indicating that the second device had an offline status when the second update was generated, the second update comprising second data, a second action, and a second timestamp;
determining that the second update and the first update are associated with a same portion of the first record;
determining that the second timestamp is prior to the first timestamp;
determining that the first record is a first type of a plurality of types of customer records stored in the database, each type of customer record defining a corresponding arrangement of data fields storing customer data;
identifying, in the same portion of the first record, one or more data fields in the arrangement of data fields corresponding to the first type of customer record;
determining, using a dependency tree data structure configured to control a sequence of records to be processed, that the first type of customer record has a parent-child relationship in the database with a second type of customer record;
determining, based on the parent-child relationship, an order for modifying the first type of customer record and the second type of customer record;
modifying the first record before or after modifying the second record of the second type of customer record according to the determined order.

2. The system of claim 1 , the database system further configurable to cause:
identifying a first update identifier associated with the first update;
identifying a second update identifier associated with the second update; and
determining that the second update identifier is different from the first update identifier.

3. The system of claim 2 , the database system further configurable to cause:
obtaining a third update to the first record, the third update received from the second device;
identifying a third update identifier associated with the third update;
determining that the third update identifier is identical to the second update identifier; and
responsive to determining that the third update identifier is identical to the second update identifier, modifying the third update to indicate that the third update is a duplicate update.

4. The system of claim 1 , wherein the second update is one of a plurality of updates received from the second device, the database system further configurable to cause:
obtaining a third update to a third record;
determining that the third record is a third type of customer record;
and
based on a dependency relationship between the second type of customer record and the third type of customer record, processing the third update prior to processing the second update.

5. The system of claim 1 , wherein the first action and the second action comprise one or more of: a search action, a subscribe action, a post feed item action, a send e-mail action, a convert action, an escalate action, a publish action, a get action, a create action, a share action, a post action, an edit action, an archive action, a delete action, an update action, a comment action, or a like action.

6. The system of claim 1 , the database system further configurable to cause:
obtaining a third update to the first record, the third update received from a third device different from the first device and the second device, the third update indicating that the third device had an offline status when the third update was generated, the third update comprising third data, a third action, and a third timestamp;
determining that the third update, the second update, and the first update are associated with the same portion of the first record;
determining that the third timestamp is prior to the first timestamp and the second timestamp; and
providing a notification to the third device indicating that the first update and the second update were processed prior to the third update, the second notification configurable to cause display, in a user interface at the third device, of a selectable first option representing the first data, a selectable second option representing the second data, and a selectable third option representing the third data.

7. The system of claim 1 , wherein the second update further comprises a status indicator associated with the second update, the status indicator capable of being displayed in a user interface of the second device.

8. A method comprising:
obtaining a first update to a first one of a plurality of records stored in a database, the first update received from a first device, the first update comprising first data, a first action, and a first timestamp;
modifying the first record according to the first action and the first data;
obtaining a second update to the first record and to a second record, the second update received from a second device different from the first device, the second update indicating that the second device had an offline status when the second update was generated, the second update comprising second data, a second action, and a second timestamp;
determining that the second update and the first update are associated with a same portion of the first record;
determining that the second timestamp is prior to the first timestamp;
determining that the first record is a first type of a plurality of types of customer records stored in the database, each type of customer record defining a corresponding arrangement of data fields storing customer data;
identifying, in the same portion of the first record, one or more data fields in the arrangement of data fields corresponding to the first type of customer record;
determining, using a dependency tree data structure configured to control a sequence of records to be processed, that the first type of customer record has a parent-child relationship in the database with a second type of customer record;
determining, based on the parent-child relationship, an order for modifying the first type of customer record and the second type of customer record;
and
modifying the first record before or after modifying the second record of the second type of customer record according to the determined order.

9. The method of claim 8 , further comprising:
identifying a first update identifier associated with the first update;
identifying a second update identifier associated with the second update; and
determining that the second update identifier is different from the first update identifier.

10. The method of claim 9 , the method further comprising:
obtaining a third update to the first record, the third update received from the second device;
identifying a third update identifier associated with the third update;
determining that the third update identifier is identical to the second update identifier; and
responsive to determining that the third update identifier is identical to the second update identifier, modifying the third update to indicate that the third update is a duplicate update.

11. The method of claim 8 , wherein the second update is one of a plurality of updates received from the second device, the method further comprising:
obtaining a third update to a third record;
determining that the third record

Assignees

• Salesforce Com Inc

Inventors

• Dandy Michael
• Zhulina Aleksandra
• Adam Abraham

Classifications

• G06F16/2372

  Updates performed during offline database operations · CPC title

• G06F16/2358

  Change logging, detection, and notification (replication G06F16/27) · CPC title

• G06F16/2322 Primary

  using timestamps · CPC title