By using entities created in the Data Service, you can manage and manipulate data aggregated in a single object, without having to work with it in a granular way. To do so you need Studio v2020.8 or later.
The following example retrieves data about Olympics games and medals for the top 10 countries for each category of games, together with the medals they won.
Following the steps detailed on the Creating an Entity page, we created an entity for storing information about participating nations, the opening and closing dates, and the medals they won.
The Olympics entity has the following fields: Name, Nations, Opening, and Closing Dates. The Medals entity has the following fields: Country, Gold, Silver, Bronze, and the total number of medals. The two entities are linked to each other with the Relationship tag.
Import the entity inside your workflow in Studio, as explained in the Importing Entities page.
The following workflow scrapes information about a certain Olympics edition, maps data to arguments, and passes them along to the main workflow.
To do so we defined an argument for each type of information that we are collecting, thus resulting in 5 imported arguments.
With the use of entities, we only need to import and work with two arguments to collect the data.
Entities must be initialized using the New Operator, read from the Data Service or passed through an input argument in a workflow before usage, otherwise assigning or reading their values can cause errors.
The collected data is mapped to the two arguments
inOlympics Year and
outOlympics and their respective properties, the same as the fields defined in the entity. By using entities we're reduced the number of arguments needed for passing along information by properly mapping data to their respective entity fields.
Once the data was collected, you can use the Create Entity Record activity to add the information to the Data Service.
In this example, we used the imported arguments to pass the collected information to the Data Service. The Input and Output records are the values of variables of type Olympics used for passing along the data.
After running the project, the following record was created in the Data Service:
Records structured in a data table can be passed along to the Data Service using the For Each Row activity. In this example, we're invoking a workflow that collects structured data on the number of medals won by each country and passes these records along to the Data Service.
After running the workflow, the following data is stored in the Data Service:
The relationship set between the Olympics and Medals entities allows us to use the data record from one in the other. For example, the value of the Olympics field inside the Medal entity is the same as in the related entity.
The Query Entity Records activity can be used to pull up a list of records from the Data Service. In the following example, we use the activity to query data records from the Olympics entity, allow the user to choose an Olympics edition, and from the Medals entity write the number of medals that each participating country won.
For querying the Olympics table, we've used the
Name != NULL condition from the Query Builder. This goes through all records from the Name column and outputs them in the
listOlympics variable to be used in the Input Dialog activity.
To show the list of records as options, we've used the following Lambda expression
listOlympics.Select(Function (o as Olympics) o.Name).ToArray in the Input Dialog activity. Alternatively, the For Each activity can be used.
The selection is mapped to the
selectedOlympics variable and used in another Query Entity Records activity for going through the list of medals won at that specific edition. This condition was set by using the
equals option in the Query Builder.
The query can be performed on the selected entity, and on related entity records as well.
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. The Top property supports a maximum number of 1,000, this means that 1,000 records can be queried at a time.
This example queries the first five records, and then the next five records until the last records on the list are grabbed.
To perform this, the
skip Int64 variable was assigned the initial value of
0, and then its value is incremented after each loop until the last record is grabbed.
After the first five medals are grabbed, the For Each activity is used for writing the participating countries and the number of medals they won to the Notepad file.
The following scenario explains the steps for updating an entity record in the Data Service and then synching the data with Studio.
In the Data Service, go to the Medals entity, click Create New Field, and add a new column HostCountry of type Yes/No. Click Save.
In Studio, click on Manage Entities, and then the Refresh button. A change was detected for the Medals entity, as illustrated in the Changes column. Click Save and the entity is updated in Studio.
The Update Entity Record activity can be used for updating records from your workflow directly into the Data Service.
In this example, we're querying certain records from the Medals entity and updating them automatically using the aforementioned activity.
In the Medals entity, the hosting country of each edition is marked with an asterisk next to its name. For example, for the 2012 edition, the hosting country is recorded as Great Britain (GBR)* in the Olympics column.
Using the Query Entity Records activity, we go through all records that contain the asterisk (*), grab the records in the
listMedals variable and use the For Each activity to loop through each item and assign the True value in the HostCountry column next to the country that hosted a particular edition.
The Update Entity Record activity can be used in numerous other scenarios for passing along data and updating records in the Data Service.
Updated about a month ago