
Use more general search terms.
Select fewer filters to broaden your search.
You are here:
This asynchronous method stores an object change related information in a queue and commits it as part of the next save action triggered by an Consumer Good (CG) Cloud offline mobile app user.
| Available in Lightning Experience in Professional, Unlimited, and Enterprise Editions that have Consumer Goods Cloud enabled. |
For example, when a module in the CG Cloud offline mobile app is closed by tapping the Back button or when a process action manually triggers a save. This method is similar to the saveTQObject method, but is applicable only when a database transaction is kept open. For example, a Consumer Goods Cloud offline mobile app user relaunched the application while the order release was in progress. The created order isn’t saved in this scenario.
object description: The information of the object
intended to be saved.
The object information includes the following parameters:
changeType: Indicates the object change status and can
have the following values: N: Indicates that the object is
to be newly created. U: Indicates that the object is to be
updated. D: Indicates that the object is to be deleted. data: Refers to the actual data to be saved in JSON
format.idAttribute: Refers to a unique key attribute within a
Salesforce object.idProperty: Refers to a unique key attribute within a
business object.name: Refers to the name of an object defined in the
Salesforce backend. mapping: Refers to the mapping between the simple
property names of a business object and the attribute names of a Salesforce object.The method returns a promise (without any information).
promise = Facade.putTrackedObjectInTransaction({
name: mapping.tableName,
idAttribute: mapping.idColumn,
idProperty: mapping.idProperty,
mapping: mapping.columnMapping,
changeType: changeType,
data: data
}).then(function () {
return when.resolve(true);
});

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.