Mapping Data Fabric (Data Service) to Test Case Arguments for Performance Testing - Cross-platform

Hi everyone,

I’m working on a Performance Testing scenario and I’m hitting a wall regarding the data binding between Data Fabric (Data Service) and Test Manager.

Context:

  • Application: UiBank Loan Application (UiBank)
  • Project Type: Test Automation (Desktop Studio)
  • Compatibility: Cross-platform
  • Data Source: Data Fabric Entity with 50 test records.

The Goal: I want to run a Performance Scenario in Test Manager where I use the 50 records from Data Fabric to feed my Test Case. I want these to run in parallel (stress test) across multiple virtual users.

What I’ve done so far:

  1. In UiPath Studio, I used the “Get Entity Record By Id” activity.
  2. I created an In Argument named in_RecordId.
  3. In Test Manager, under the Performance Scenario, I selected Data Source → Data Service and chose my Entity (50 records).

The Issue: I am struggling to find the correct way to “bridge” the Id from Data Fabric to my Studio argument.

  • Should the argument in_RecordId be of type String or Guid in a Cross-platform project?
  • How do I ensure that Test Manager “sees” this argument in the Data Variation / Mapping section of the Performance Scenario? Currently, the mapping table doesn’t seem to populate correctly even after “Update Automation”.

What is the recommended activity/property configuration in Studio to receive the ID from Test Manager dynamically?

In this case, it’s usually easier to keep in_RecordId as String in the Studio test case

Also check:

  • in_RecordId is an In argument in the test case
  • the project is republished
  • Update Automation is run again in Test Manager so it refreshes the arguments

Then you can map the Entity Id to in_RecordId in the Data Variation section.

Regards,
Dhruba

What is the recommended activity/property configuration in Studio to receive the ID from Test Manager dynamically?

Hey @Alexandru_Duta

To answer your question on how to bridge Data Fabric with Performance Testing—the key is to not manually create the in_RecordId argument yourself.

When you import the Data Fabric entity in Studio via Manage Entities and set the test case data source to Data Service, Studio automatically generates a typed argument like ProjectName.EntityName for you. This argument holds the entire entity record, not just the Id.

The default value you will see is:

System.Text.Json.JsonSerializer.Deserialize(Of ProjectName.EntityName)

This is UiPath deserializing the full record at runtime. You access fields simply as EntityName.FieldName.ToString().

Then in Test Manager, when setting up your Performance Scenario, add your test case to a Load Group and configure the Data Fabric entity as the data source at the Load Group level. Test Manager will automatically distribute one record per virtual user and run them in parallel—no manual Id mapping needed.

One important thing—do not rename the auto-generated argument, as that will break the data binding completely.

We need to implement the test case in Studio the same way we do with data-driven testing using Data Service / Data Fabric.

Hope this helps!

Thanks,
Karthik