Multiple create, update, or delete requests MUST NOT run concurrently, and should instead be run sequentially. Furthermore, this API will have the following effects (if these features are enabled):

• run PSL Object Triggers for the record(s) in question

• process SFDC ValidationRules for the record(s) in question

• re-calculate and save formula fields for the record(s) in question

• re-calculate roll-up summary fields on parent object(s) records(s) for record(s) in question

var request = {
    "type" : "create",
    "object" : "Account",
    "data" : { "Name" : "John Doe Industries", "Phone" : "867-5309" },
	"args" : { 
		"allowEditOnFailure" : "FALSE", // OPTIONAL : DEFAULT IS "TRUE"-- Allow editing the record using the Pulsar object edit screen to fix errors on a create failure
		"skipLayoutRequiredFieldCheck" : "FALSE" // <-- OPTIONAL : if specified as "TRUE", will avoid checking for missing layout required fields
	}};
bridge.sendRequest(request, function (responseData) { 
	alert('Javascript got its create response: ' + responseData); 
});

Multiple create, update, or delete requests MUST NOT run concurrently, and should instead be run sequentially. Furthermore, this API will have the following effects (if these features are enabled):

• run PSL Object Triggers for the record(s) in question

• process SFDC ValidationRules for the record(s) in question

• re-calculate and save formula fields for the record(s) in question

• re-calculate roll-up summary fields on parent object(s) records(s) for record(s) in question

var request = { 
    "type" : "update",
    "object" : "Account",
    "data" : { "Id" : "001234567891234", "Name" : "John Doe Industries, Inc", "Phone" : "(555) 867-5309" },
              // Id is a required field to identify the record to update
    "args" : {
        "skipLayoutRequiredFieldCheck" : "FALSE" // OPTIONAL : if specified as "TRUE", will avoid checking for missing layout required fields
    }
};
bridge.sendRequest(request, function (responseData) {
 

   alert('Javascript got its 

update response: ' + responseData);

});

Multiple create, update, or delete requests MUST NOT run concurrently, and should instead be run sequentially. Furthermore, this API will have the following effects (if these features are enabled):

• run PSL Object Triggers for the record(s) in question

• process SFDC ValidationRules for the record(s) in question

• re-calculate and save formula fields for the record(s) in question

• re-calculate roll-up summary fields on parent object(s) records(s) for record(s) in question

The deletebatch API allows efficiently deleting multiple objects, provided as an array of object Ids. See the example syntax below.

var request = { 
    "type" : "deletebatch",
    "object" : "Account",
    "data" : { "objectIdList" : [ "001234567891234","001234567891235","001234567891236" ] } // only Ids are required
};
bridge.sendRequest(request, function (responseData) {
    console.log('Javascript got its response: ' + responseData);
  
    

if 

(results.

type === "deletebatchResponse") {
     

var 

resultObject = results.data;
  

Sample response:

{
    "type": "deletebatchResponse",
    "object": "Account",
    "fieldName": 

null,
    "data": {
        "

summary": {
            

"

success": "

FALSE"

        },
        "

results": 

{
            

"

001234567891234": 

{
            

"objectId": "001234567891234",
   

             "success": "TRUE",
     

The select request allows advanced users to create an arbitrary select query using Pulsar's built in database engine. 

var request = { 
    "type" : "select",
    "object" : "Account",
    "data" : { "query" : "Select Id from Account Where Name like '%hello%'" }
};
bridge.sendRequest(request, function (responseData) {
    alert('Javascript got its select response: ' + responseData);
});

We encourage you to use the standard CRUD updaterequest, (see above).  The updateQueryrequest allows developers to issue a raw UPDATE to the local database.

Caveat Programmer!

updateQueryis an advanced request for custom/batch updates, and extreme care should be taken with its use

• Does not perform processing of ValidationRules for the record(s) in question

• Will not re-calculate and save formula fields for the record(s) in question

• Will not re-calculate roll-up summary fields on parent object(s) records(s) for record(s) in question

• It is possible to write values to the Db offline that will not sync cleanly to Salesforce or may damage your Salesforce instance when synced

• It is possible to write values to the Db that will break functionality across the Pulsar app

When Pulsar is in online mode, the updateQuery request will attempt to push the resulting database changes to your Salesforce instance. Responses to the updateQuery request will always reflect the success or failure of the local database query, even if the push to Salesforce has failed. In this situation, errors from Salesforce are reported as part of the success response (see example below), and the results of the query are maintained in the local database as offline changes.

var request = { 
    "type" : "updateQuery",
    "object" : "Account",
    "data" : { "query" : "UPDATE Account SET ActiveCustomer__c = 'TRUE' WHERE OpportunityCount__c > 0;" }
};
bridge.sendRequest(request, function (responseData) { 
	alert('Javascript got its update query response: ' + responseData); 
});

Response: {
    "type": "updateQueryResponse",
    "object": "Account",
    "data": 

"

success",

   "

errors"

: 

[

       {
            "errorCode": "ENTITY_IS_LOCKED",
            "message": "This record is locked. If you need to edit it, contact your admin."
        }
    ]
}