Saving New Objects¶
In order to determine if an object needs to be stored as new or the existing one should be updated, Backendless checks if the object in the API call has the
objectId value. This principle is used in the save and update API as well as in the Deep Save API. Below are some of the examples demonstrating various scenarios:
When using the Deep Save API to save new objects, make sure the tables are defined in the database. If the table does not have a column defined for a non-relational property in your object, the API will return an error.
Parent/Child Objects with one-to-one Relation¶
The sample below stores parent (
Product) and child (
Manufacturer) objects in the corresponding tables and creates a relationship between the objects in the database:
Once the code runs, the following two objects are stored in the Manufacturer and Product tables:
Object in the
Object in the
Parent/Child Objects with one-to-many Relation¶
In the example below the parent object (
Order) contains two relations: one is a one-to-one relation to a
Customer object and the other is a collection (а one-to-many relation) of child objects (
OrderItem). The Deep Save API stores the parent object, the children and establishes a relationship in the database between the parent and its children:
When the Deep Save operation completes, the database will have the following objects:
||Name of the data table where a new record must be saved or updated.|
||An object to save or update in the database. Object properties must match the names of the table columns.|
||Optional parameter. When this box is checked, the operation returns the saved or updated object with the
The Deep Save API allows saving new objects or updating existing ones in the specified data table. You can easily save or update objects that have relations, this includes: parent objects and child objects.
Returns the saved object with the
objectId property assigned by Backendless. This object has the other nested objects containing the related data.
Consider the structure of the data table called
"orders" column is configured to have one-to-many relations with objects stored in the
Orders data table:
Orders data table contains the
"items" column where the order details are stored in the JSON format.
The example below saves a new object to the
Customers data table. This object has two nested objects containing the related data that will be saved to the
Orders data table, since initially the one-to-many relation was set in the
Customers data table.
After the Codeless logic runs, the new object gets saved to the
Customers data table. As you can see, now the
"orders" column is active and has relations to two other objects stored in the
Orders data table.
Two other objects stored in the
Orders data table contain order information in the
The result of this operation will look as shown below after the Codeless logic runs: