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 another article discussing user management, we covered how to use the user registration API to register users for your app. When registering a user, your app sends a collection of user registration properties to the server. Values for these properties typically come from a registration form in your app. Some form fields may be…
Any file in the Backendless File Storage is also accessible through a public URL. This functionality can be restricted by changing security settings.
In another post, we introduced you to the publish/subscribe messaging API. The API can be used to broadcast messages that can be received by multiple client apps. Note: It is important to distinguish between pub/sub messages and Push Notification messages. There are a number of technical differences and purposes where an app should use one…
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.
This is an introductory post for a very broad feature – injecting custom server-side logic into Backendless. There are a lot of smaller features in Cloud Code (also known as Custom Business Logic), but it’s worth it to start with a general overview.
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.
In another post, we described a feature for conditional pub/sub message delivery using SQL selectors. With that (selector) approach, the publisher must attach headers to the message and the subscriber uses an SQL-based condition that references header names and values. In addition to selectors, Backendless supports another type of conditional delivery – subtopics.
The Backendless Geoservice supports a variety of ways to search for geopoints. So far we have reviewed how to search for geopoints in a radius or a rectangular area. There is also a partial match geopoint search. In addition to that, Backendless Console provides yet another way to search for data – the cross-category search….