Assistance Required: Migrating UiPath Data Service Integration from Development to Production

[pavithra_pavi (Pavithra Bhat)]

Hello All,

I need some guidance regarding UiPath Data Services.

I have a requirement where records need to be added to a Data Service entity on demand. We are working across two separate tenants:

1. Development
2. Production

I have already built and tested the process in the Development tenant, where data is successfully uploaded to the relevant Data Service entity.

However, I’m now facing a challenge during the migration to Production. In the “Create Entity Record” activity, the entity name must be selected from a dropdown list, and cannot be dynamically passed using a variable. Additionally, due to company policy, we are not allowed to install UiPath Studio on the Production server.

Given these constraints, could anyone suggest a recommended approach to migrate the solution from Development to Production while ensuring the Data Service integration works seamlessly?

Note: the studio version im using is 2024.10.9

Any insights would be greatly appreciated.

[Nikhil_Zambare1 (Nikhil Zambare)]

Dear @pavithra_pavi,

Right entity activities do not accept custom string/varaibles. We have to select the entity name at the design time only.

Additionally, no need to install the studio on production server.
You can use same devlopment studio to connect with production tenant.

For this, follow below steps:

1. Create user in production tenant.
2. Allocate automation devloper lincese to newly created use for temporary purpose.
3. Connect devlopment studio to production tenant via machine key or interactive login.
4. Once logged in into studio, you can see production tenant entities in studio.
5. Publish the package & deploy your process.

Mark as solution, if it solves your issue

Br,
NikZ

[rall (R)]

Replicate the entity across environments by exporting the schema (exports ALL entities and choice sets) from Development, then when importing in Production you can select the specific entities/choice sets to import.
Relevant documentation: Data Service - Schema export and import

[rall (R)]

And in your code, you can freely refer to the entity in Development. Last I checked, the files within the .entities folder reveals that it mentions tenant by name, but this method works for my team and the automations run in prod as expected despite never being connected to that environment at design-time.