studio
2022.4
false
- 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
- 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
- Studio testing
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User

OUT OF SUPPORT
Studio User Guide
Last updated Jul 16, 2025
Example of Using DataTable Variables
linkTo exemplify how you can use DataTable variables, we are going to create an automation that reads only two out of multiple columns from an Excel spreadsheet, and then transfers them to another spreadsheet that already contains other information.
The initial file is a database of people, transactions, dates, and products. In this example, we are going to extract their names and order dates and append them to an Excel spreadsheet that already contains similar information.
- Create a new sequence.
- Add an Excel Application Scope activity to the sequence. This activity is required for most of the Excel-related activities.Note: If you do not have Excel activities installed on your version of UiPath, use the Manage Packages functionality to get them.
- Create two DataTable variables,
NamesList
andDateInfo
. These are going to be used to store information from the initial Excel spreadsheet. - In the Properties panel, in the WorkbookPath field, type the path of the initial Excel file to be used, between quotation marks.
- Add two Read Range activities and place them one under the other, in the Excel Application Scope activity. These are used to get information from the initial spreadsheet.
- Select the first Read Range activity and, in the Properties panel, in the Range field, type "G7:G37". These are the Excel table coordinates that tell UiPath Studio from where to extract information.
- In the SheetName field, do not make any changes as the name of our sheet is the default one, Orders.
- In the DataTable field, type the name of the first DataTable variable,
NamesList
. This variable stores all the information available between the G7 and G37 rows. - (Optional) Change the value in DisplayName field to Read Names, so you can easily tell apart this activity from the second one.
- Select the second Read Range activity, and in the Properties panel, in the Range field, type "C7:C37". These are the Excel table coordinates that contain the order date we want to extract.
- In the DataTable field, specify the
DateInfo
variable. This variable retains all the date information we require. - In the Activities panel, under System > File > Workbook, add a Write Range activity to the Designer panel, under the Excel Application Scope. This activity is used to write the stored information to another Excel file.Note: The file used with the Write Range activity has to be closed when you run the project. If it is not closed, an error is displayed and the automation execution stops.
- In the Properties panel, in the WorkbookPath field, type the path of the Excel file to be used to store all the information gathered at the previous steps.
- In the DataTable field, type the
NamesList
variable. - In the SheetName field type Database, and in the StartingCell, type "B7.“ This is the starting cell in which information from the initial file is to be added.
- Add another Write Range activity and place it under the first one.
- In the Properties panel, fill in the WorkbookPath and SheetName fields as for the previous Write Range activity.
- In the Starting Cell field, type "A7".
- In the DataTable field, type the
DateInfo
variable. - Press F5. Your automation is executed.
- Double-click the final Excel file. Note that the copied information is available, and correctly updated.