- Release notes
- Before you begin
- Managing access
- 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
- Process simulation
- 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
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing process apps
- Publishing process apps
- App templates
- Notifications
- Additional resources
Process Mining
If you have multiple Event tables, these can be added to the data model one-by-one and they are merged automatically. Check out Viewing and editing the data model for more information on how to add tables.
Alternatively, you can manually merge Event tables using the following queries.
If your event log is split over multiple event log files, you can merge the event logs into a single event log in Data transformations.
To merge multiple event logs, the Case_ID should point to the same object for all files. For example, all Case IDs are pointing to Sales Order IDs., such that Case_ID points to the same table for all event logs.
-
Create a new app, based on the Event log app template. Check out App templates.
-
Use the Upload data option in the Selecting the Data Source step, and select the event log files you want to merge.
-
Continue the Create new app wizard to create the app and to transform the data.
The data run will fail and the Application status will show Run failed.
-
Select View log to view the log file.
An error message displays indicating that the expected file is not found. -
Go to the Data transformations editor.
-
For each input file:
-
Create a
.sqlfile with the same contents as the already availableEvent_log_input.sql. -
Adjust the file to select the required input fields and type cast them correctly.
-
Add the name of the new source tables to
sources.yml.Now all new input files can be combined into a single event log.
Attention:Make sure that the input files all have the exact same set of fields.
-
-
Select the
Event_log_input.sqlfile and replace the contents with:-- The following code merges 3 input tables. select * from {{ ref('Event_log_input_1') }} union all select * from {{ ref('Event_log_input_2') }} union all select * from {{ ref('Event_log_input_3') }}-- The following code merges 3 input tables. select * from {{ ref('Event_log_input_1') }} union all select * from {{ ref('Event_log_input_2') }} union all select * from {{ ref('Event_log_input_3') }}Note: Adjust the code to match the names of the input tables needed. -
Select Apply to dashboards to run the data transformations and make the resulting table available for use in the dashboards.
