For each entry in a given table, Backendless creates a unique
objectId property – this is a UUID. In some cases, you may want to have a unique ID based on a whole number. To do this, we will use Backendless Atomic Counters (you can read the documentation about Atomic Counters here). In this article, we will use JavaScript business logic to create a handler that will add a unique value before creating the object. You can then store that value in your table to provide the ID you’re looking for.
Amazon Elasticsearch Service (Amazon ES) is a service that can store a lot of data and provide a full text-based search, among other cool features. In this article, we’ll show you how to integrate Amazon ES with your Backendless project.
Save objects to Amazon ES
To save objects to the Amazon ES with Backendless you have to:
- Create an Amazon ES domain
- Create after event handlers in the Backendless console
- Download generated code
- Write JavaScript code to save objects
It is very easy to use Backendless with Xamarin, Microsoft’s open source native app builder. You can try out Xamarin for building apps for free with the Community edition of Visual Studio from Microsoft. In this post, we’re going to create a simple example based on the Xamarin ToDo list sample provided by Xamarin.
Suppose your app logs in a user. As a result, the app gets user-token which uniquely identifies the user’s session with Backendless. If your app uses our SDK for Android, iOS, JS or .NET, the user-token value is managed directly by our libraries. Specifically, it is added to every API call to maintain the session and tell the server about the user’s identity. There are situations when you need to get the user object when your app has only user-token. This could happen if you used persistent login in the application, which stores user-token on the device. The implementation does not save the user object, however, there is a way to retrieve the user based on the user-token value (assuming the token is still valid). In this article, I will show you how to do this.
The technique for retrieving the user object is creating an API service which accepts a user-token in the header and retrieves the current user. I will use Codeless to create the API service because it has an intuitive interface and allows you to solve these tasks very quickly, just by building the algorithms instead of writing code:
