- Release notes
- April 2026
- March 2026
- February 2026
Data Fabric release notes
Data Fabric now onboarded to Solutions
This release introduces significant enhancements to UiPath Data Fabric, as part of its onboarding to Solutions. These updates expand access control capabilities, enable multi-scope entity and choice set management, and deeply integrate Data Fabric entities with Solutions, streamlining how automation assets are packaged and deployed across your organization.
What's new
- Tenant- and folder-level entities - Entities can now be scoped to a tenant or a specific Orchestrator folder, enabling fine-grained data isolation.
- Entity relationships and choice sets scope - Scoping for entity relationships and choice sets.
- Solutions integration - Data Fabric folder-level entities used in a Solution are automatically included as resources during package creation and deployment.
- New Orchestrator permissions for folder-level entities - Three new permission types, Entity Records, Entity Schema, and Entity Roles enable granular access control.
- Entity-level RBAC (Role-Based Access Control) - Folder-level entities now support role-based access control configured directly in Data Fabric.
1. Tenant- and folder-level entities
Data Fabric now supports creating entities at two distinct scopes:
| Scope | Visibility | Behavior |
| Tenant | All users with tenant access | Same as previous behavior; entities are globally accessible within the tenant. |
| Folder | Users with access to the selected Orchestrator folder only | Entities are isolated to the folder and not accessible outside of it. |
When creating an entity, a new Location field appears in the creation dialog:
- Select Tenant to create a globally visible entity.
- Select Folder and choose the required Orchestrator folder to create a folder-scoped entity.
This update enables teams working in multi-tenant or multi-project environments to isolate data entities by team, project, or business unit, reducing cross-team data exposure.
2. Entity relationships and choice sets scope
Relationship scoping rules now 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.
- 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.
| Role | Impact |
| Schema Designer | You must have access to the related entity's or choice set's folder to include it in a schema. |
| Data Reader | You 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 Writer | You 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 Developer | You 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 User | Permissions are evaluated at execution time. The operation completes fully or partially depending on which folders you have access to at the time of execution. |
3. Solutions integration
Data Fabric entities are now fully integrated with Solutions, eliminating the need to manually recreate entities during package deployment.
Automatic resource inclusion
- When a folder entity is used in a Solution, it is automatically added as a Solution resource.
- Manual entity recreation steps previously required during deployment are no longer necessary for folder-level entities.
Packaging and deployment
- When a package is deployed to a folder, any required entities are created automatically:
- Folder-level entities are created in the target folder.
- Tenant-level entities, if not already present, are created at the tenant level if packaged via Orchestrator.
- Tenant-level entities used in a workflow are not automatically packaged or published — they must already exist in the target environment for the deployed workflow to function as expected.
Studio Web behavior
- When using Data Service activities in Studio Web, select the folder entity scope for the entity context.
- Only entities from folders where the user has access are displayed.
- Folder-level entities used in workflows are automatically added to the Solution.
Override is supported at two stages: during debug, when a workflow is being built in Studio Web, and during runtime, after the workflow is packaged, deployed, and the RPA process is being executed.
During debug - the entity used can be kept as-is, replaced with a different existing entity, or removed entirely. If the selection is removed, a new entity, along with its dependencies, is created in the Personal Workspace to support the debug execution.
During runtime - the override options are limited: the workflow can run on the existing entity or be mapped to a different existing entity. Creating a new entity at runtime is not supported.
Entity relationships
If Entity A is related to Entity B, both entities are automatically added as Solution resources.
Override is only available for resources directly referenced from an activity. By default, this applies to Entity A. Entity B is not eligible for override unless it is referenced directly from an activity via Platform resources, not Defined resources.
- In both cases, the override functionality allows entities used in a workflow to be mapped to existing entities with a compatible schema from a different folder.
- Mapping across tenants is not supported.
- When using override during debug and runtime, ensure the replacement entity maintains the required relationships to avoid schema mismatch errors.
4. New Orchestrator permissions for folder-level entities
- Entity Records — Controls access to the data stored in the entities within the folder (read, write, delete).
- Entity Schema — Controls access to the structure and schema definition of the entities within the folder.
- Entity Roles — Controls management of roles assigned to the entities within the folder.
5. Entity-level RBAC (Role-Based Access Control)
Entity-level RBAC, previously available for tenant-level entities, can now also be configured for folder-level entities directly in Data Fabric under Manage Access. This provides an additional layer of control on top of Orchestrator folder permissions. To configure entity-level RBAC, take the following steps:
- On the Entities page, select Manage Access.
- Select the Roles tab.
- Select Create new role, and then choose Folder entities role from the dropdown.
- Add a Role Name and then choose the Folder location.
- Select the entities you want from the Add Entity dropdown, and then define permissions for them.
- Assign the role to users or groups.
- Folder access in Orchestrator is the first-level control. Entity-level RBAC is applied as an additional security layer on top of folder permissions. Users must have folder access in Orchestrator before RBAC rules take effect.
- Permission changes are subject to a two-minute cache. A short delay in permission sync may be observed after access is updated.
Support and limitations
Supported
- Data Service activities in Studio Web.
- Studio Web-based automation workflows.
- Apps (VP Apps) using Data Service tenant entities.
- Studio Desktop.
- Data Fabric accessed via connectors.
- Maestro or API-based workflows.
- Entities with fields that fetch data exclusively from external systems.
- Entities with fields combining local UiPath-stored data and external system data.
- Cross-scope relationships between tenant and folder entities are not supported in this release.
- Overriding a related entity during deployment requires that the replacement maintains compatible schema relationships to avoid mismatch errors.
- Two entities with the same name cannot be added to the same workflow.
- Folder-level entities are not supported in Unified Projects.
- To refresh the schema of a folder-level entity selected in a Data Service activity, the entity must be reselected from the dropdown under Platform resources, not Defined Resources.
- Cross-folder reference entities cannot be packaged.
- Folder-level choice sets are not available.
Locale-aware date format in Data Explorer
Data Explorer now displays date and datetime field values using a format that matches the user's selected language preference, instead of a fixed format.
DD/MM/YYYY format, regardless of the user's language setting. After this update, the format adapts to the active language:
| Language | Date format |
| Engllish (en) | MM/DD/YYYY |
| Spanish (es) | DD/MM/YYYY |
This is a display-only change within Data Explorer. It does not affect:
- Underlying stored data
- API responses
- UiPath Studio activities
- Automation workflows that consume data via API or activities