Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Using $Component to Reference Components from JavaScript
Using JavaScript Libraries with Visualforce
JavaScript Remoting for Apex Controllers
Visualforce Remote Objects
A Simple Example of
Using Visualforce Remote Objects in JavaScript
Creating Records with
Retrieving Records with
Updating Records with
Upserting Records with
Deleting Records with
Format and Options for Visualforce Remote Objects Query Criteria
Visualforce Remote Objects Callback Functions
Overriding Default Visualforce Remote Objects Operations
An Example of Using Visualforce Remote Objects with jQuery Mobile
Best Practices for Using
Visualforce Remote Objects Limits
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Upserting Records with

Save a record by calling upsert() on a Remote Objects model instance.

upsert() is a convenience function that updates a record if it exists and creates it if it doesn’t. Behind the scenes upsert() delegates to create() or update(). Use upsert() to write functions for your page or application that aren’t affected by whether a record is from a new input form or an edit record page.

upsert() accepts two arguments, both optional.
1RemoteObjectModel.upsert({field_values}, callback_function)
The field_values block enables you to set the values and save a record in one statement. Set field values as you do when you create a model, using a JSON string. For example, the following two calls to upsert() are equivalent.
1// Call upsert() on a Contact model, with no arguments
2// ct is a RemoteObjectModel.Contact that already has data
3ct.set('Phone', '(415) 777-1212');
4ct.upsert();
5
6// Call upsert() on a Contact model, passing in field values
7// ct is a RemoteObjectModel.Contact that already has data
8ct.upsert({Phone: '(415) 777-1212'});

In the preceding example, it’s not clear if the contact exists in the database or if it’s a new contact that’s coming from an input form. upsert() handles the details. If there’s an Id field set on the contact, the contact will be updated. If there’s no Id, a new contact is created.

upsert() doesn’t return a result directly. The callback function enables you to handle the server response asynchronously.

All server operations that use Remote Objects are performed asynchronously. Any code that depends on the request being completed, including handling returned results, must be placed in the callback function.

Note

Your callback function can accept up to three arguments.
1function callback(Error error, Array results, Object event) { // ... }
See Callback Functions Callback Functions for details about writing Remote Objects callback functions.