In this article, we’ll consider some practical examples of how to use the Backendless Data Collection library to its fullest extent. You can find code documentation and sources for the library here.
One of our key standard features is the ability to send emails through Backendless Console. We offer prebuilt email templates or you can create your own email template. In this article, we will show you how to do the latter.
In another post, we describe how data tables in Backendless map to the client-side classes whose instances contain persisted data objects. However, there are scenarios when the default mapping is undesirable. In that case, Backendless client libraries provide an API to override the mapping.
In another article, we wrote how to load the first object from a data table using API. For the purpose of symmetry (and out of common sense), there is also an API to load the last object from a data table in your Backendless Database. The last object is determined by the time when it is…
Data objects in Backendless can be connected to related properties not only in other tables, but also with Geopoints. These relationships may be declared programmatically or using Backendless Console. In this post, we will review the process of declaring a Data-to-Geo relationship in a data table schema.
Whether you develop with IntelliJ IDEA, Eclipse, or Android Studio, the Backendless library (jar) for Java/Android must be referenced as a dependency. The library includes all the APIs that provide access to the backend functionality. The library is deployed to the centralized Maven repository, which makes it easy to import it to any Backendless-powered app.
Geolocation is one of the most powerful features of Backendless. The geolocation service provides APIs for storing, searching and managing geolocation data. There are three main elements that the geolocation service operates on: geocategories, geopoints, and points metadata.
In a previous post, we described how to use the custom business logic code generator to create Backendless timer code. The previous post left off at the step when the Backendless Console created the code.
In a previous post, we wrote about Backendless server-side timers – blocks of code which run on a pre-defined schedule. A timer is a Java class and can be created by hand. The most tedious part is figuring out the scheduling definition. Currently, this is done by declaring the timer’s schedule through a JSON object…