In this Blog Post, We have covered every details about Newly Introduced Data Services component of UiPath RPA tool. Topics Included are as below-
Let’s get started.
This Blog is meant to show step by step guide to Use newly introduced Data Service from UiPath.
To experience the full features Data Service and follow along the demos in this course, you need an Enterprise account in UiPath Automation Cloud.
If you don’t have such a plan, you can start an Enterprise Trial now and use it after Enabling the Data Service for your Tenants.
In 20.10 LTS, Data Service will become available both on-premises and through the Automation Cloud for community.
If you wish to follow the code example shown in this blog post, You can download that from the GitHub URL.
Following along with the code is the best thing to do when you are trying your hands on a new concept in UiPath.
To start using the Data Service you need an Automation Cloud account, and You need to enable Data Service for the tenant you wish to use.
You can Enable the Data Service using below steps –
Once you select the Data Service, you need to Update License so that Data Service Gets reflected at Admin Dashboard.
It might take few minutes, before it gets refreshed and once this is done you will be able to see screen like below.
So far so good, Now you should be able to create your New Entity on Data Service.
We will look at How to create an entity, manage the relationship and other stuff in the next section when we work on Example of Suppliers and Products Entity.
But this is pretty simple steps all you need to do is define the Fields and their Datatype.
Please Note – All the Action on Data Service are based on user authorization and it will inherit Your permissions based on their configured roles/groups.
You can read more about roles and grants on Data Service UiPath Documentation – How to Configure required access setup for Data Service.
Let’s talk about, where we can use Data Services in a real-life example. I have listed a few sample use cases but it can be extended to many scenarios where storage and persistence data is required.
Data Service provide you additional storage capability for your intelligent automation projects so that you can integrate your business data with UiPath Different components on the fly.
You must be thinking, why we need additional storage capability for Storing RPA projects data while you can connect/dump/export data to Relational databases, No SQL Databases, file or even on cloud storage.
Why do we need additional layer of Data Services for Consuming the data in RPA projects?
Below is some common use case where we can fit in Data Services –
For Example: #Bot1 perform some task in CRM to create entry, Waits for Human to complete the next steps and then #Bot2 resume the task based on status. In this case, we can create two related Entity to track the status of Work done by #Bot1 and perform tasks accordingly.
Through the use of multiple related entity all different kind of request can be processed effectively and within SLA adherence without putting much data (Master Tables) exposed to RPA.
For example, Customer Account Closure example, where customer various steeps need to be followed in Different application, In all such cases we can create parent child relationship entity to perform sub-tasks and then update status in parent to get task completed.
For this part of Blog, We have taken the example of Products and suppliers where we will go through the following steps.
Let’s work on the first Dataservice Working Example.
The benefit of using entities created in the Data Service is that you can manage and manipulate data aggregated in a single object.
[See Example below, where 5 Fields are system built-in type and rest others are created as per need.]
[In the Below, Example SupplierID is the Display name which creates a relationship with Suppliers entity]
So far we have created, Two entities which are shown below, for Using them inside the studio you need to perform the following steps.
Navigate to all Packages, Search UiPath.DataServices.Activities, Click Install and Save.
You will be able to search Data Services Activities now.
Entities are available for import in Studio v2020.8 +; If you are not able to see the option on ribbon button you might need to update your studio.
The imported entities can now be used locally in your project as objects. After importing entities in your workflow, its namespace is imported as well and you can find it in the Imported Namespaces list shown below.
When you run the workflow and check data tab on Cloud portal, You should be able to see the created entities records.
The Query Entity Records activity can be used to pull up a list of records from the Data Service.
Data services can potentially store a large number of records. To query only a certain number of records, use the Pagination properties from the Query Entities Records activity.