In another article, we reviewed how to register app users with the API. By default, a Backendless backend declares a user entity with three properties: email, password, and name. The “email” property is configured as identity by default, meaning its value should be passed into the login API request.

When saving or updating a data object in a persistent storage, it is often necessary to make sure a property follows a particular data format. For instance, properties like email address, a US phone number, a bank account number, a URL and many others may be validated with regex (a regular expression). Backendless makes it…

Backendless File storage can be used to host web applications. The file storage includes a special directory – “/web” which is used to host web application content. Since the default URLs for files in your file storage are rather long and use the backendless.com domain, it may be desirable to map a custom domain name…

In another post, we wrote about how to create developer-defined security roles and how to secure data table access for a security role. Ultimately when a client application makes API requests, the security evolves around users, since it is a user who authenticates themselves against the system.

Previously, we wrote about how to store and retrieve objects to and from server-side in-memory cache. Quite often when working with your cache, it is necessary to check if an object already exists in cache. Backendless provides an API for that function. The code below checks if an object exists in cache, and if not,…

In another post, we described how to declare a relationship in a data table schema with a geopoint. Now that you know how to create a table column that contains one or more geopoints, we are going to show how to populate it with data.

We’ve written about how to upload files to the Backendless Hosting system. Once a file is uploaded, it gets a public URL which can either be obtained using Backendless Console or calculated using a template.

In another article, we described how a data object may have a related geopoint (or a collection of geopoints). One of the benefits of data-to-geo relationships is search by distance. That means Backendless can search for data objects using the location of the related geopoints.

Connecting users with their related data is a key function of user management. When you register (or update) a user object, you may need to create a relation between the user and some other entity/object stored in your Backendless Database. Since a user object is structurally a collection of properties, it is very easy to…