UiPath Documentation
data-service
latest
false
  • Getting started
    • Introduction
    • Exploring the user interface
    • Regions and instances
  • Licensing
  • Setup and configuration
  • Using the service
    • Creating an entity
    • Customizing an entity
    • Managing the data for an entity
    • Creating relationships
    • Choice sets
    • System User Entity
    • Schema export and import
    • Advanced search in entity data
    • Using Apps
    • Known limitations
  • Reference
  • Examples and tutorials
  • Logging
important :
Data Service is currently transitioning to Data Fabric, a process during which you may see both names used for different delivery options.
UiPath logo, featuring letters U and I in white
PREVIEW

Data Fabric user guide

Last updated Apr 2, 2026

Creating relationships

To create a relationship between your entities, take the following steps:

  1. In the Entities list, select the entity for which you want to add a relationship.
  2. Select Manage Entity.
  3. In the Local fields section, select Add field and provide a Display name and a Name. Select Relationship from the Type dropdown. The Advanced options panel opens.


  4. Select the entity for which you want to create a relationship from the Related Entity dropdown list.
  5. Select the display field to be shown in the user interface from the Related Entity Display Field dropdown list.
  6. Select Apply.

The relationship is added as a new field in the Local fields section.

When adding data you can select values from the related entity.

Scope restrictions

Relationship scoping rules apply as follows:

  • Tenant-level entities can only be related to other tenant-level entities.
  • Folder-level entities can only be related to entities in folders where the user has access.
  • Cross-scope relationships (Tenant to Folder or Folder to Tenant) are not supported.
Choice sets support the same tenant/folder scoping as entities:
  • Tenant-level choice sets are visible to all users within the tenant.
  • Folder-level choice sets are accessible only within the selected folder.
  • Visibility and usage rules mirror entity scoping for consistent data isolation.
Entity AEntity BSupported
TenantTenantYes
Folder AFolder AYes
Folder AFolder B (accessible)Yes
TenantFolderNo
The following table describes how folder-level scoping affects each role when working with related entities or choice sets.
RoleImpact
Schema DesignerYou must have access to the related entity's or choice set's folder to include it in a schema.
Data ReaderYou must have access to both the parent and related entity folders to query complete data. Without access to both, the related field is omitted from results.
Data WriterYou must have access to both the parent and related entity folders to write to related fields. If access to the related folder is missing, the data write is partial. If a related field is marked Required, the data write fails entirely for users without full access.
Automation DeveloperYou must have access to both the parent and related entity to use that entity in a workflow. Partial access prevents the entity from being used.
Automation UserPermissions are evaluated at execution time. The operation completes fully or partially depending on which folders you have access to at the time of execution.
  • Scope restrictions

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated