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…

In other articles, we have covered: how to declare a geo-to-data relationship in a data table schema and how to create relationships between an object in that schema and geopoints. Of course, both of the operations above can also be accomplished with the API. In this post, we are going to show how to retrieve…

In another article, we covered importing data table schemas, relations and data objects to Backendless with CSV files. The data import feature can also work with geolocation storage. The process is extremely simple – browse to a CSV file with the geolocation data and let Backendless process it.

In other articles, we have reviewed multiple techniques for loading data objects from persistent server-side storage. There is a list of all articles categorized by topic. In this post, we are going to review the API for loading data objects using an SQL query.

Deleting an object in your Backendless Database using the Data Service API is just as easy as creating or updating one. If an object has relations, they are broken up and the related objects are not deleted. The sample below retrieves the first object from a table and deletes it.

Data paging is the process of breaking up a larger set of objects into smaller chunks, commonly referred to as pages. Typically paging applies to the results of search queries when the server may return too many objects at once.

In another article, we wrote about how to save Backendless data objects with related geopoint(s). The data-to-geo relations are bidirectional. That means that just as a data object can reference a geopoint (or more than one) as a relation, a geopoint may reference a data object or a collection of in its metadata as well.

In this article, we’re going to review a fun feature – an ROI (return on investment) calculator. That may sound like a boring subject, but we sure tried to make it fun. Indeed, if you are a developer and are tasked with figuring out how a product or a service can save money, it may…