- 入门指南
- 许可
- 设置和配置
- 使用服务
- 参考
- 示例和教程
- 日志记录
Folder-level Data Fabric entities in Studio Web and Studio Desktop for building workflows inside a Solution.
Folder-level Data Fabric entities are available in Studio Web and Studio Desktop (26.10 LTS) when working inside a Solution. In the classic activities, folder scope requires UiPath.DataService.Activities v26.10.0 or later, where it is generally available. This page covers how to select and configure entities in the Studio environment. For the full lifecycle — packaging, deployment, overrides, upgrade, and uninstall — refer to Entities in Solutions.
Selecting an entity scope
Each Data Service activity includes a scope selector. The scope determines which entities are available:
- Tenant — Shows entities available across the entire tenant.
- Folder — Shows a tree of all Orchestrator folders where you have access, along with the entities in each folder.
Folder scope is not available in a local workspace on any surface. It is available in cloud workspaces only.
Schema refresh
A Refresh button is available next to the entity selector. Selecting Refresh updates the schema of the selected entity and all of its related entities (child entities) in a single action.
The Refresh button behaves differently depending on the activity type:
- Connector activities (Data Fabric connector) — The Refresh button is always enabled. To see newly added or removed fields after a schema change:
- Open the Solution resource for the entity and select Update Configuration to pull the latest schema into the Solution.
- Return to the activity and select Refresh Schema to load the updated fields.
- Classic activities (Data Service classic package) — The Refresh button is enabled only when a schema change is detected for the selected entity. Selecting it updates the schema directly.
自动资源包含（预览）
When you use a folder-level entity in a Data Service activity inside a Solution, the entity is automatically added as a Solution resource. All dependencies — related entities, choice sets, and their nested dependencies — are included automatically. You do not need to add them manually.
Studio Web
- Select the Folder scope in the activity to work with folder-scoped entities.
- 工作流中使用的文件夹级别实体会自动添加到解决方案中。
- During debug, you can override entity bindings, use existing entities, or create new ones in your Personal Workspace.
Studio 桌面
Studio Desktop 26.10 LTS supports folder-level entities when working with Solutions. Use the same scope selector to choose between tenant and folder entities. This requires UiPath.DataService.Activities v26.10.0 or later.
Studio Desktop support applies to folder-level entities used in a Solutions context.
Debug and runtime overrides
Entity overrides are available at two stages:
During debug — In the Debug configuration window, you can keep the existing entity, replace it with a compatible entity from another folder, or remove the selection to create a new entity in your Personal Workspace.
At runtime — After deployment, change entity bindings in Orchestrator via Package Requirements without republishing.
Deploy-time override is not supported.
Override is available only for entities directly referenced from an activity. A related entity (for example, Entity B referenced through a relationship field) is not overridable unless you add a separate activity that references it directly from under Platform resources.
- Override allows mapping to a compatible entity from a different folder. Mapping across tenants is not supported.
- Ensure the replacement entity maintains compatible schema relationships to avoid mismatch errors.
Supported surfaces
| 表面 | Folder-scoped entities |
|---|---|
| RPA (Studio Web) | ✅ |
| RPA (Studio Desktop 26.10 LTS) | ✅ (Solutions context, UiPath.DataService.Activities v26.10.0) |
| Maestro BPMN | ✅ |
| Maestro 案例 | ✅ |
| API 工作流 | ✅ |
| Agents (智能体) | ✅（预览版） |
| Maestro 流程 | Via native entity nodes |
| Coded Apps | ✅ |
| 编码智能体 | ✅ |
| Standalone VB Apps | ❌ |
| RPA (UB) Apps | ❌ |
| Local Workspace | ❌ |