ExamFinch.com My Study

Study guide

22.1 Data Fabric (Data Service) Entities: Modeling Business Data

Practice this exam

UiPath Automation Developer Professional UiPath-ADPv1

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Blueprint Map

1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan

2 Chapter 2: REFramework Architecture & State Dynamics

2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes

3 Chapter 3: REFramework Exception Handling & Recovery

3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination

4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing

4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues

5 Chapter 5: LINQ Queries & DataTable Operations

5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations

6 Chapter 6: Regex, DateTime, JSON & Invoke Activities

6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments

7 Chapter 7: Modern UI Automation & Unified Targeting

7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors

8 Chapter 8: Object Repository, Computer Vision & Remote Runtime

8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime

9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS

9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript

10 Chapter 10: Advanced Control Flow & Exception Architecture

10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures

11 Chapter 11: Orchestrator Queues & Transaction Management

11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers

12 Chapter 12: Orchestrator Tenant & Folder Entities

12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance

13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

14 Chapter 14: Monitoring, Recording & Solutions Management

14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources

15 Chapter 15: Debugging, Remote Debugging & Profiling

15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio

16 Chapter 16: RPA Testing & Test Suite

16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability

17 Chapter 17: Long-Running Workflows, Action Center & Apps

17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service

18 Chapter 18: Trigger-Based Attended Automation & Callouts

18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance

19 Chapter 19: UiPath Assistant & Robot Sessions

19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop

20 Chapter 20: Autopilot for Developers & Autopilot for Everyone

20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI

21 Chapter 21: API Automation & Integration Service

21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows

22 Chapter 22: Data Service, Context Grounding & Coded Workflows

22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services

23 Chapter 23: Integrated Scenario Practice

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

22.1 Data Fabric (Data Service) Entities: Modeling Business Data

Key Takeaways Explain This Topic AI

Data Service is transitioning to the name Data Fabric; entities store business data with typed fields for automations and apps.

An entity's Name (3 to 30 characters, starting with a letter), type (Native or Federated), and Location (tenant or folder) cannot be changed after creation.

Field types are Text, Multi-line text, Number, Yes/No, Date-Time, Choice set, Relationship, File, and Auto-number.

Standard roles are Administrator, Designer, Data Writer, and Data Reader, and the Everyone group can read by default.

CSV import does not support relationship, choice set, or auto-number data; schema export and import support moving definitions between environments.

Last updated: September 2026

22.1 Data Fabric (Data Service) Entities: Modeling Business Data

Core Concept: Data Service is transitioning to the name Data Fabric , and you may see both names. It is UiPath's persistent, no-code data store for automations and apps. Data is modeled as entities with typed fields, and automations work with whole records instead of dozens of loose variables. The exam description lists Data Service entities under resource management.

Why Use Entities

One version of the truth across attended and unattended processes, for example storing invoices once and passing only the record ID through queues.

Long-running processes that move data across several jobs and human steps.

Aggregation: one unattended process gathers data from several systems, and other processes read it from Data Fabric instead of every user needing access to every system.

Cleaner workflows: model a Customer entity, import it in Studio, and work with one typed variable.

Creating an Entity

  • Setting Rules
  • Display Name Shown when you import the entity in Studio; can be changed later
  • Name Alphanumeric, starts with a letter, 3 to 30 characters; cannot be changed after creation

Entity type Native (data stored in UiPath, full create, read, update, and delete) or Federated (a read-only view whose fields come from external systems, such as Salesforce or SAP through connections, or from a native entity)

Role-based record access Optional toggle to restrict access to individual records (not for Federated entities)

Location Tenant (available to all users with tenant-level access) or Folder (visible only to users of the selected Orchestrator folder); cannot be changed later

The entity type is also fixed once chosen.

Field Types

  • Field type Holds
  • Text / Multi-line text Strings; short or long
  • Number Integers or decimals
  • Yes/No Boolean values
  • Date-Time Dates and times
  • Choice set One or more values from a predefined list (choice sets are defined separately and reused)
  • Relationship A link to a record of another entity
  • File A file attached to the record
  • Auto-number A generated sequential number

Records also carry system fields such as the record Id and who created or updated them and when.

Access Control

Manage Access assigns roles to users and groups.

Standard roles: Administrator , Designer , Data Writer , and Data Reader . Standard roles cannot be removed, and custom roles can be created.

By default, organization users can read data through the Everyone group. To restrict data, adjust that access and assign roles deliberately.

Folder-level entities are additionally limited to users of their Orchestrator folder.

Managing Data and Schemas

Add, edit, and delete records in the Data Fabric interface, or import data from CSV . Import requires Read and Create permissions and does not support relationship, choice set, or auto-number fields, which must be non-required for import to work.

Schema export and import moves entity and choice set definitions between tenants for development, test, and production.

Advanced search filters records in the interface.

Using Entities in Studio

In Studio, import the entities you need. Each entity becomes a type in the project, for example Invoice .

Declare variables of that type, such as inv As Invoice , and set fields directly: inv.VendorName = "ACME" .

Use the Data Fabric activities, such as Create Entity Record , Query Entity Records , and Update Entity Record , which the next section covers.

When the entity's schema changes, update the imported entities in Studio so the types match.

Designing Good Entities

Model business objects , such as Invoice, Supplier, and Claim, not screens.

Use relationships instead of copying data between entities, for example Invoice to Supplier.

Use choice sets for statuses so values stay consistent across processes and apps.

Choose the location deliberately: use Folder entities to keep departmental data separate.

Keep large documents in File fields or storage buckets , and keep searchable data in typed fields.

Worked Example

An invoice solution uses:

Supplier (Name, TaxId, Country as a choice set).

Invoice (Number as Auto-number, Supplier as a relationship, Amount as Number, Status as a choice set, PDF as a File field).

The dispatcher creates Invoice records and adds only the record Id to the queue. The performer reads the record, processes it, and updates Status. An approval app shows the same record to reviewers, and a reporting process queries all invoices with Status "Exception".

Common Traps

Picking Tenant location for departmental data and then trying to move it to a folder; the location cannot be changed.

Expecting to write to a Federated entity; it is read-only.

Leaving the default Everyone read access in place for sensitive entities.

Making relationship or choice set fields required and then failing a CSV import .

Changing the entity schema without updating the imported entities in Studio.