Learn how to store and sync data with QuickBlox key-value storage.
Custom Objects module provides flexibility to define any data structure (schema) you need, build one-to-many relations between schemas and control permissions for all operations made on data. The schema is defined in QuickBlox Dashboard.
Visit Key Concepts page to learn the most important QuickBlox concepts.
To view a list of classes, follow the steps below:
To create a custom object class, follow the steps below:
To delete a class, follow the steps below:
To add a field to a class, follow the steps below:
To remove a field from a class, follow the steps below:
To view a list of records, follow the steps below:
To add a custom object record, follow the steps below:
You can create a child record. A child record is a record that refers to another record that has already been created, a parent. When a record is created, it is assigned a record ID. Thus, you can create a new record, a child, and attach it to the parent record by pointing to its ID. See this section to learn more about relations between records. To create a child record, follow the steps below:
To edit a record, do the following:
To remove a record, follow the steps below:
You can set a permissions schema. There are two access levels in the permissions schema: class and record. Only one permission level can be applicable to the record: class permission schema or record permission schema.
Only the account owner can create a class in the Custom Objects module and make all possible actions with it.
All actions (Create, Read, Update, and Delete) are available for the class entity and are applicable for all records in the class. Every action has a separate permission level available. The exception is a Create action that is not available for the Owner permission level. See this section to learn about permission levels.
Default class permission schema is used while creating a class:
To set a permissions schema for the class, do the following:
A class permission schema has a higher priority than a record permission schema. If an account owner ticks the Use Class permissions checkbox, the record permissions are ignored.
In case, an account owner doesn’t tick the Use Class permissions checkbox, a user has a possibility to change permission levels for every separate record in the table or create a new one with the ACL that a user requires.
A record is an entity within the class in the Custom Objects module that has its own permission levels. All permission levels except for the Not Allowed are available for the record and there are only three actions available and applicable for the record: Read, Update, and Delete. See this section to learn more about permissions.
Default Record permission schema is used while creating a class:
To set a permissions schema for the record, do the following:
A class permission schema has a higher priority than a record permission schema. If an account owner ticks the Use Class permissions checkbox, the record permissions are ignored. See this section for more details.
You can import data in CSV or JSON format. To import data, do the following:
You can import a class schema. The class schema defines class fields and their data types in .yml format. To import a class schema, do the following:
Learn how to store and sync data with QuickBlox key-value storage.
Custom Objects module provides flexibility to define any data structure (schema) you need, build one-to-many relations between schemas and control permissions for all operations made on data. The schema is defined in QuickBlox Dashboard.
Visit Key Concepts page to learn the most important QuickBlox concepts.
To view a list of classes, follow the steps below:
To create a custom object class, follow the steps below:
To delete a class, follow the steps below:
To add a field to a class, follow the steps below:
To remove a field from a class, follow the steps below:
To view a list of records, follow the steps below:
To add a custom object record, follow the steps below:
You can create a child record. A child record is a record that refers to another record that has already been created, a parent. When a record is created, it is assigned a record ID. Thus, you can create a new record, a child, and attach it to the parent record by pointing to its ID. See this section to learn more about relations between records. To create a child record, follow the steps below:
To edit a record, do the following:
To remove a record, follow the steps below:
You can set a permissions schema. There are two access levels in the permissions schema: class and record. Only one permission level can be applicable to the record: class permission schema or record permission schema.
Only the account owner can create a class in the Custom Objects module and make all possible actions with it.
All actions (Create, Read, Update, and Delete) are available for the class entity and are applicable for all records in the class. Every action has a separate permission level available. The exception is a Create action that is not available for the Owner permission level. See this section to learn about permission levels.
Default class permission schema is used while creating a class:
To set a permissions schema for the class, do the following:
A class permission schema has a higher priority than a record permission schema. If an account owner ticks the Use Class permissions checkbox, the record permissions are ignored.
In case, an account owner doesn’t tick the Use Class permissions checkbox, a user has a possibility to change permission levels for every separate record in the table or create a new one with the ACL that a user requires.
A record is an entity within the class in the Custom Objects module that has its own permission levels. All permission levels except for the Not Allowed are available for the record and there are only three actions available and applicable for the record: Read, Update, and Delete. See this section to learn more about permissions.
Default Record permission schema is used while creating a class:
To set a permissions schema for the record, do the following:
A class permission schema has a higher priority than a record permission schema. If an account owner ticks the Use Class permissions checkbox, the record permissions are ignored. See this section for more details.
You can import data in CSV or JSON format. To import data, do the following:
You can import a class schema. The class schema defines class fields and their data types in .yml format. To import a class schema, do the following: