If a data table in your application has a column of the DATETIME type, the values for that column will be rendered by Backendless Console in mm/dd/yyyy hh:mm:ss format. For many applications, and specifically in some industries like telecommunications or finance, it is important to see the date objects in a “neutral” format and often…
In another post, we described how to restrict access to all data for “guest” users. The Backendless security model lets you control access to data tables, or more generally “asset containers”, at the role and operation levels. That means an application developer can set up security restrictions for API operations on a specific data table…
Data objects stored in Backendless Database may have related objects through one-to-one or one-to-many collections. When objects are retrieved on the client-side, these relations are materialized as collections of data in the object’s fields or properties.
A user on StackOverflow asked how to load only the data that belongs to the currently logged-in user. This is indeed an interesting and very common use-case. Backendless handles it beautifully and this feature certainly deserves a place among our Recipes.
In a previous feature, we described how to manually create data tables in Backendless Console. In this post, we will show how to set up a data table schema.
The article that shows how to store objects in Backendless also demonstrated dynamic data table creation. That approach is called “code first” – where the code dictates the database schema.
In another post, we showed how to update data objects in the persistent storage. In this post, we’ll talk about declaring the minimum required properties needed to update objects.
Every data object saved in Backendless has its own access control list (ACL). An object’s ACL includes permissions for users and roles for all data service operations. Using ACL, an application may be configured to allow users (and/or roles they belong to) to execute Data Service API calls.
In this post, we will show how to save an object with relations in Backendless Database. We are using the “code first” approach, which means we will not be creating data tables in the backend. Instead, the code will dictate to the backend what the data schema should look like.