Using Mobile Sync in JavaScript
To use Mobile Sync in a hybrid app, import these files with <script> tags:
jquery-*x.x.x*.min.js
(use the version in thedependencies/jquery/
directory of the SalesforceMobileSDK-Shared repository)underscore-*x.x.x*.min.js
(use the version in thedependencies/underscore/
directory of the SalesforceMobileSDK-Shared repository)backbone-*x.x.x*.min.js
(use the version in thedependencies/backbone/
directory of the SalesforceMobileSDK-Shared repository)cordova.js
force.js
mobilesync.js
To begin using Mobile Sync objects, define a model object to represent each SObject
that you want to manipulate. The SObjects
can be standard Salesforce objects or custom objects. For example, this code creates a model of the Account object that sets the two required properties—sobjectType
and fieldlist
—and defines a cacheMode()
function.
Notice that the app.models.Account
model object extends Force.SObject
, which is defined in mobilesync.js
. Also, the cacheMode()
function queries a local offlineTracker
object for the device's offline status. You can use the Cordova library to determine offline status at any particular moment.
Mobile Sync can perform a fetch or a save operation on the model. It uses the app’s cacheMode
value to determine whether to perform an operation on the server or in the cache. Your cacheMode
member can either be a simple string property or a function returning a string.
The model collection for this sample app extends Force.SObjectCollection
.
This model collection uses an optional key that is the name of the account to be fetched from the collection. It also defines a config()
function that determines what information is fetched. If the device is offline, the config()
function builds a cache query statement. Otherwise, if no key is specified, it queries the most recently used record ("mru"). If the key is specified and the device is online, it builds a standard SOQL query that pulls records for which the name matches the key. The fetch operation on the Force.SObjectCollection
prototype transparently uses the returned configuration to automatically fill the model collection with query records.
See querySpec for information on formatting a cache query.
These code examples are part of the Account Editor sample app. See Account Editor Sample for a sample description.