Saving Multiple Objects

This API stores multiple objects in a data table with a single request. Consider the following example, it demonstrates an API call which saves two objects in the Person data table:

List<Map<String, dynamic>> persons = new List();

Map<String, dynamic> person1 = {
  "age": 24,
  "name": "Joe",
};
persons.add(person1);

Map<String, dynamic> person2 = {
  "age": 34,
  "name": "Betty",
};
persons.add(person2);

Backendless.data.of("Person").create(persons).then((response) {
    print("Objects have been saved");
});

The result of running the sample above is two objects saved in the database:

Method

Using MapCustom Class

Future<List<String>> Backendless.data.of("TABLE-NAME").create(List<Map> objects);

Future<List<String>> Backendless.data.withClass<E>().create(List<E> objects);

where:

Argument	Description
TABLE-NAME	Name of the table where the objects expressed via Map instances will be saved.
E	Dart class of the data objects to save in the database.
objects	A collection of Dart objects to save in the database, must be of type E or Map (depending on the method used).

Return Value

The API returns a collection of object IDs for the objects created in the database. The order of  the objectId values in the response matches the order of the objects in the request.

The Backendless server implementation enforces the following rules:

Rules
All objects in the request must be of the same type.
Objects in the request may have different set of properties. A property in the request body is ignored, if a column does not exist in the table.
Objects in the request may have a unique objectId value that is not used in the database.
Maximum number of objects in a single request is 100 for Backendless Cloud. It is configurable for Backendless Pro and Managed Backendless.
A request will be rejected by the server, if there is no Create permission granted to the user identity/roles associated with the request.

Codeless Reference

where:

Argument	Description
table name	Name of the data table where new records must be saved.
objects	Must be a list containing objects to save in the database. Object properties must match the names of the table columns. The object must not have the objectId property.
Return created objectIds	Optional parameter. When this option is selected, the operation returns a list containing one or more objectId values , depending on the number of saved objects.

Returns a list containing one or more objectId values, depending on the number of saved objects.

Consider the following structure of the data table called employees:

For demonstration purposes, the data table presented above has three custom columns: name, position, and phoneNumber. The objectId is a system column that contains unique identifiers of the records in the table. When a new record is saved to the table, the system assigns a unique objectId to it. The objectid is used in various operations as an access point to a specific record.

The example below saves two new objects to the employees data table:

The result of this operation will look as shown below after the Codeless logic runs:

The operation described above has returned a list containing two objectId values associated with the newly created records: