- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- Publishing process apps
- App templates
- Additional resources
Editing and testing data transformations
Refer to the pages listed below for more information on editing data transformations.
Run all is limited to one hour. Therefore, it is strongly recommended to use a small dataset for the development and testing of data transformations, to make sure your transformations do not exceed this time limit. See also: Process Mining portal.
cases_input.sql
has been modified. The Run all command would run cases_input.sql
and cases.sql
, which uses the results of cases_input.sql
.
The resulting data will only be available in the Data Transformations editor, not in the dashboard editor.
There are two types of runs:
-
Run all: starts a data run, recalculating all modified queries, and their dependencies.
-
Run file: starts a run to recalculate only the currently selected SQL file and its parent queries. This option enables you to test and debug customizations to specific SQL files.
You can select Cancel run at any time to cancel the transformations run.
Run all is typically much faster than Apply to dashboards which starts a full data run.
Run all does not affect the data in the published process app.
You can create new folders and add new files in your transformations.
-
For names of files, folders, fields, and tables:
-
you can only use lowercase (a-z) characters, uppercase (A-Z) characters, and numbers (0-9);
-
you cannot use special characters
|*:?"<>\/
for names of files, folders, fields, and tables.
-
-
For file names, you can only use
_:.
as special characters. -
A file name cannot start with an
_
(underscore).
Follow these steps to create new folder or file.
Steps |
Action |
---|---|
1 |
Navigate to the location in the transformations where you want to add a new file or folder. |
2 |
Go to the Transformations panel and select the menu icon to open the transformations menu. |
3 |
Select the applicable option from the menu. |
4 |
Enter a descriptive name for the new folder or file and select Enter. |
The new folder or file is created in the selected folder.
Follow these steps to create new folder or file from the context menu.
Steps |
Action |
---|---|
1 |
Right-click on the folder in the transformations where you want to add a new file or folder. |
2 |
Select the applicable option from the menu. |
3 |
Enter a descriptive name for the new folder or file and select Enter. |
Follow these steps to create new folder or file.
Steps |
Action |
---|---|
1 |
Right-click on the folder or file you want to rename to open the context menu. |
2 |
Select Rename. |
3 |
Edit the name as desired and select Enter. |
The folder or file is renamed.
Follow these steps to create new folder or file.
Steps |
Action |
---|---|
1 |
Right-click on the folder or file you want to delete to open the context menu. |
2 |
Select Delete. A confirmation message is displayed. |
3 |
Select Delete to confirm the deletion. |
{# ... #}
. This also enables you to comment macros.
{# {{ pm_utils.optional(ref('Cases_base'), '"Case_status"') }} as "Case_status", #}
{# case
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} >= 1000000
then {{ pm_utils.as_varchar('>= 1M') }}
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} >= 0
then {{ pm_utils.as_varchar('0 - 1M') }}
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} is not null
then {{ pm_utils.as_varchar('< 0') }}
end as "Case_value_group", #}
{# {{ pm_utils.optional(ref('Cases_base'), '"Case_status"') }} as "Case_status", #}
{# case
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} >= 1000000
then {{ pm_utils.as_varchar('>= 1M') }}
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} >= 0
then {{ pm_utils.as_varchar('0 - 1M') }}
when {{ pm_utils.optional(ref('Cases_base'), '"Case_value"', 'double') }} is not null
then {{ pm_utils.as_varchar('< 0') }}
end as "Case_value_group", #}
In the Data Transformations editor, you can find and replace texts inside a single file.
-
Click on a random place in the code editor, or select the text you want to search for other occurrences.
-
Press
CTRL+F
. -
Enter the test you want to search for in the Find field.
All occurrences of the text in the current file are highlighted.
-
Select
ENTER
to skip to the next occurrence.
-
Click on a random place in the code editor, or select the text you want to search for other occurrences.
-
Press
CTRL+H
. -
Enter the test you want to search for Find field and enter the new test in the Replace field.
All occurrences of the text in the current file are highlighted.
-
Select
ENTER
to replace the text and skip to the next occurrence.
-
Click on the code editor.
-
Press
CTRL+H
. -
Enter the test you want to search for Find field and enter the new test in the Replace field.
All occurrences of the text in the current file are highlighted.
-
Press
Crtl+Alt+Enter
.
If you want to Find/replace texts in multiple files, you can only do this in an external editor.
Follow these steps to Find/replace texts in multiple files:
-
Export transformations from your process app.
-
Unzip the transformations.
-
Open the transformations in your favorite code editor, for example, Notepad++, or Visual Studio Code.
-
Use the functionality of those tools to find or replace texts in multiple files.
-
Save the files.
-
Add the transformation files to a .zip file.
-
Import the transformations in your process app.
When you are asked which data to use for a data run, select Cancel if you want to continue editing transformations before doing a new data run.
dbt_project.yml
.
vars
section, if required. The other parts of the dbt_project.yml
should not be changed to ensure the transformations keep working properly.
For detailed information on dbt, see the official dbt documentation.
To make the changes available in the dashboards, you must execute a full data run to load the data and run the transformations. Select the Apply to dashboards button to start a data run.
Depending on the size of your dataset, this make take some time.
After a successful data run, the new transformations become available in the dashboard editor and can be used to adjust the dashboards.
- Editing transformations
- Running the queries
- Adding folders and files
- Naming conventions
- Creating a new folder or file from the transformations menu
- Creating a new folder or file from the context menu
- Unsaved changes in files
- Renaming a folder or file
- Deleting a folder or file
- Adding comments in files
- SQL
- Find / replace in files
- Find text
- Find and replace
- Find/replace in multiple files
- Editing dbt project configuration files
- Making the transformations available in dashboards