- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Importing Entities
Entities enable you to use records from the UiPath Data Service, a centralized data modelling and storage service. Entities can be used in automation processes that collect, update, and pass data to other processes. All project types can be used for importing and working with such business objects.
To import an entity:
- Open the Data Manager, then expand the Entities node. All available entities are displayed.
-
Right-click an entity, and then select Import. If you want to import all entities, right-click the Entities node instead.
The Manage Entities window opens.
-
Select the entity you want to import. To find a specific entity, use the Search Entities bar and type the entity name, display name, or description.
You can hover over the entries in the Fields column to see all the defined fields of each entity, or click the number of fields or records for an entity to navigate to the corresponding page in the Data Service.
- Enter a namespace for the imported entity. The default namespace is the same as the project name. The namespace can only be edited the first time you import an entity.
-
Click Save to import the entity in your project.
Note: If you make any changes to the entity at the level of the tenant, use the Refresh button inside the Manage Entities window before actually importing it.
Imported entities are visible in the Project panel as objects part of your project.
The imported entities can now be used locally in your project as objects. If you want to perform CRUD operations on them in the Data Service as well, you need to install the UiPath.DataService.Activities pack.
After installing the UiPath.DataService.Activities pack, drag and drop an entity on top of a plus sign in the Designer panel to use the recommended activities from the pack.
Drag and drop an entity from the Project panel into the Variables or Arguments panel to create a variable or argument with the entity type.
You can manage the imported entities from the Project panel by right-clicking the namespace or an entity, and then selecting from the context menu to manage entities, remove the namespace, or remove the entity.
After you import an entity in your workflow, its namespace is imported as well. You can find it when you browse for types under Referenced assemblies.
All fields part of an imported entity are available as properties for the entity namespace. Thus, when working with entities the number of variables or arguments for managing data is reduced.
StockPortfolio
, its properties visible in the Data Manager panel are the same as the fields defined in the entity and available as properties for the argument.
Check out the Using Entities in Projects page to see how to use them.