Salesforce Com, Inc.

Susan S Levine

Tyler Ziemann

James Hang

Neeraj Ahuja

Danil Dvinov

Michael Dandy

Simon Y Wong

Arun Kumar Jagota

Parth Vijay Vaishnav

Eli Levine

Chenghung Ker

Pawan Nachnani

David Hacker

Michael Starukhin

Steven deRochemont

Osvaldo Rene Canel Lopez

Dan Milbrath

Gaurav Salkar

Amanda Hatker

Disclosed embodiments are related to Application Programming Interface (API) technologies, and in particular, to Order APIs that are used to make modifications and cancelations to existing order objects. The Order APIs can be used to retrieve the current state of an order object, retrieve the summarized state of an order object as of a specified date, and retrieve a potential state of an order object along with specified changes. The Order APIs are also used to process order changes including changes to the quantity of an existing order object and applying line item changes to an existing order object. Other embodiments may be described and/or claimed.

Change order application programming interfaces

Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

Data object aggregation to manage an order summary

Matching objects using keys based on match rules is described. A system generates a match rule key based on a match rule, wherein the match rule specifies whether two objects match. The system creates candidate keys by applying the match rule key to data objects. The system creates a probe key by applying the match rule key to a probe object. The system determines whether the probe key matches a candidate key. The system determines whether the probe object matches a candidate object based on applying the match rule to the probe object and the candidate object if the probe key matches the candidate key corresponding to the candidate object. The system identifies the probe object and the candidate object as matching based on the match rule if the probe object matches the candidate object.

Matching objects using keys based on match rules

In accordance with embodiments, there are provided mechanisms and methods for synchronizing data in a database network system. These mechanisms and methods for synchronizing data in database network system can enable embodiments to provide users a synchronization button on a UI or synchronization field through an API for specifying data for synchronization. The ability of embodiments to provide users a synchronization button on a UI or synchronization field through an API for specifying data for synchronization can enable users to easily and efficiently change and update data in a database system.

Methods and systems for synchronizing data in a multi-tenant database environment

Systems and methods are provided for cleaning data in a customer relationship management system. A system receives a plurality of records from an on-demand system. The system identifies a record from the plurality of records that matches a stored record for a customer relationship management system. The system determines whether to update the stored record using the identified record. The system updates the stored record using the identified record in response to a determination to update the stored record using the identified record.

Method and system for cleaning data in a customer relationship management system

In a method, system, and computer-readable medium having instructions for customizing standard formula fields, at least a portion of a formula is received for a standard database field of a standard database entity in a multi-tenant database and the standard database entity is used by a plurality of tenants, a date range is stored for maintaining at least the portion of the formula, information on one or more variables of the formula is received, a value is calculated for the standard database field with at least the portion of the formula and information on the one or more variables of the formula and one or more database entities depend on the value for the standard database field, and the value is stored for the standard database field.

Customizing standard formula fields in a multi-tenant database system environment

Methods and systems are provided for synchronizing field values in transient data objects, such as JAVA&#xae; objects, before saving a transaction to a database. A dependency from one data object to another data object is detected, and changes which affect the second data object's fields through the dependency are flowed through to the second data object. This is performed between each step of a multistep save process, such between triggers, validation rules, workflows, and the final committing of data to the database.

Growing community of inventors

San Francisco, CA, United States of America

Susan S Levine