Exporting and Importing Data in QPR ProcessAnalyzer - Revision history

Ollvihe: /* Importing and Exporting .PACM File */

2022-07-25T10:48:27Z

Importing and Exporting .PACM File

← Older revision		Revision as of 10:48, 25 July 2022
Line 30:		Line 30:

	== Importing and Exporting .PACM File ==		== Importing and Exporting .PACM File ==
	QPR ProcessAnalyzer models can be exported into ~~'''~~.pacm files~~'''~~ (QPR ProcessAnalyzer compressed model file format) in the [[QPR_ProcessAnalyzer_Project_Workspace#Exporting_Model\|Workspace]].		QPR ProcessAnalyzer models can be exported into .pacm files (QPR ProcessAnalyzer compressed model file format) in the [[QPR_ProcessAnalyzer_Project_Workspace#Exporting_Model\|Workspace]].

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe: /* Importing and Exporting .PACM File */

2022-07-25T10:47:58Z

Importing and Exporting .PACM File

← Older revision		Revision as of 10:47, 25 July 2022
Line 30:		Line 30:

	== Importing and Exporting .PACM File ==		== Importing and Exporting .PACM File ==
	QPR ProcessAnalyzer models can be exported into '''.pacm files''' (QPR ProcessAnalyzer compressed model file format) in the ~~models list by clicking '''Export .pacm''' for a model. Pacm files can be imported as new models in the models list by hovering a project and in the menu selecting '''Import model from .pacm'''.~~		QPR ProcessAnalyzer models can be exported into '''.pacm files''' (QPR ProcessAnalyzer compressed model file format) in the [[QPR_ProcessAnalyzer_Project_Workspace#Exporting_Model\|Workspace]].

	Pacm file contains one model including case and event attributes and model specific user rights. If importing a model from a .pacm file to the same database from which the model was exported, all data in the .pacm file is imported. If importing from a .pacm file to a different database than from which the model was exported, the following restrictions apply:
	* Imported filters are restricted to those that were made by the user that exported the model.
	* Model specific user rights are imported if the same UserID-Username combination exists in the target database.
	* Users with the global administrator role in the source database aren't given any access rights to the model in the target database unless they also have model specific access rights in the source database, in which case only these model specific access rights are copied.

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe: /* Export Data to CSV File */

2022-03-28T23:07:08Z

Export Data to CSV File

← Older revision		Revision as of 23:07, 28 March 2022
Line 5:		Line 5:

	== Export Data to CSV File==		== Export Data to CSV File==
	Datatable contents can be exported to a CSV file, in {{QPR_ProcessAnalyzer_Project_Workspace#Opening_Datatable\|opened datatable contents]]. Click ''Settings'' and ''Export as.. in the ''Analyze'' tab.		Datatable contents can be exported to a CSV file, in [[QPR_ProcessAnalyzer_Project_Workspace#Opening_Datatable\|opened datatable contents]]. Click ''Settings'' and ''Export as.. in the ''Analyze'' tab.

	[[QPR_ProcessAnalyzer_Chart\|Chart]] is able to export data that it's presenting to a CSV file, available in the ''Visual'' tab in the chart settings. You can choose to show any process mining objects such as events, cases and event types. When there is lot of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in a dashboard. Chart can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export separately.		[[QPR_ProcessAnalyzer_Chart\|Chart]] is able to export data that it's presenting to a CSV file, available in the ''Visual'' tab in the chart settings. You can choose to show any process mining objects such as events, cases and event types. When there is lot of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in a dashboard. Chart can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export separately.

Ollvihe: /* Importing .XES File */

2021-06-28T13:32:49Z

Importing .XES File

← Older revision		Revision as of 13:32, 28 June 2021
Line 10:		Line 10:

	== Importing .XES File ==		== Importing .XES File ==
	~~.xes~~ files [http://www.xes-standard.org/#ieee_1849-2016_xes_standard eXtensible Event Stream standard] can be imported to QPR ProcessAnalyzer. The file format is interpreted as follows:		Xes files [http://www.xes-standard.org/#ieee_1849-2016_xes_standard eXtensible Event Stream standard] can be imported to QPR ProcessAnalyzer. The file format is interpreted as follows:
	* ''Trace entities'' are imported as cases		* ''Trace entities'' are imported as cases
	** The immediate child entity of trace entity having '''concept:name''' as the value of key-attribute is imported as the case id.		** The immediate child entity of trace entity having '''concept:name''' as the value of key-attribute is imported as the case id.

Ollvihe: /* Export Data to CSV File */

2021-06-28T13:32:37Z

Export Data to CSV File

← Older revision		Revision as of 13:32, 28 June 2021
Line 5:		Line 5:

	== Export Data to CSV File==		== Export Data to CSV File==
	~~[[ChartView]]~~ can ~~export any data that is presented in tables~~ to CSV, ~~when clicking the~~ '''~~CSV Export~~''' ~~button~~. ~~You can choose two show any process mining objects such as events, cases and event types~~. ~~Also datatable contents can be exported~~.		Datatable contents can be exported to a CSV file, in {{QPR_ProcessAnalyzer_Project_Workspace#Opening_Datatable\|opened datatable contents]]. Click ''Settings'' and ''Export as.. in the ''Analyze'' tab.

	When there is ~~lots~~ of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in ~~the UI, and that's why ChartView has~~ a ~~limitation of 10 000 rows by default~~. ~~ChartView~~ can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export ~~file~~ separately.		[[QPR_ProcessAnalyzer_Chart\|Chart]] is able to export data that it's presenting to a CSV file, available in the ''Visual'' tab in the chart settings. You can choose to show any process mining objects such as events, cases and event types. When there is lot of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in a dashboard. Chart can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export separately.

	== Importing .XES File ==		== Importing .XES File ==

Ollvihe: /* Importing Data from CSV File */

2021-06-28T13:27:29Z

Importing Data from CSV File

← Older revision		Revision as of 13:27, 28 June 2021
Line 2:		Line 2:

	== Importing Data from CSV File ==		== Importing Data from CSV File ==
	Data from CSV files can be imported to datatables ~~in QPR ProcessAnalyzer in~~ the [[Importing_Data_to_Datatable_from_CSV_File\|Workspace]].		Data from CSV files can be imported to datatables using the [[Importing_Data_to_Datatable_from_CSV_File\|Import dialog in the Workspace]].

	== Export Data to CSV File==		== Export Data to CSV File==

Ollvihe: /* Importing and Exporting .PACM Files */

2021-06-28T11:12:09Z

Importing and Exporting .PACM Files

← Older revision		Revision as of 11:12, 28 June 2021
Line 29:		Line 29:
	** Other values are converted into string using invariant culture		** Other values are converted into string using invariant culture

	== Importing and Exporting .PACM ~~Files~~==		== Importing and Exporting .PACM File ==
	QPR ProcessAnalyzer models can be exported into '''.pacm files''' (QPR ProcessAnalyzer compressed model file format) in the models list by clicking '''Export .pacm''' for a model. Pacm files can be imported as new models in the models list by hovering a project and in the menu selecting '''Import model from .pacm'''.		QPR ProcessAnalyzer models can be exported into '''.pacm files''' (QPR ProcessAnalyzer compressed model file format) in the models list by clicking '''Export .pacm''' for a model. Pacm files can be imported as new models in the models list by hovering a project and in the menu selecting '''Import model from .pacm'''.

Ollvihe: /* Importing .XES Files */

2021-06-28T11:12:01Z

Importing .XES Files

← Older revision		Revision as of 11:12, 28 June 2021
Line 9:		Line 9:
	When there is lots of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in the UI, and that's why ChartView has a limitation of 10 000 rows by default. ChartView can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export file separately.		When there is lots of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in the UI, and that's why ChartView has a limitation of 10 000 rows by default. ChartView can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export file separately.

	== Importing .XES ~~Files~~ ==		== Importing .XES File ==
	.xes files [http://www.xes-standard.org/#ieee_1849-2016_xes_standard eXtensible Event Stream standard] can be imported to QPR ProcessAnalyzer. The file format is interpreted as follows:		.xes files [http://www.xes-standard.org/#ieee_1849-2016_xes_standard eXtensible Event Stream standard] can be imported to QPR ProcessAnalyzer. The file format is interpreted as follows:
	* ''Trace entities'' are imported as cases		* ''Trace entities'' are imported as cases

Ollvihe at 11:11, 28 June 2021

2021-06-28T11:11:55Z

@@ Line 2: / Line 2: @@
 == Importing Data from CSV File ==
-Data from CSV files can be imported to QPR ProcessAnalyzer using the [[Importing_Data_to_QPR_ProcessAnalyzer|Data import]] view. It's possible to import:
+Data from CSV files can be imported to datatables in QPR ProcessAnalyzer in the [[Importing_Data_to_Datatable_from_CSV_File|Workspace]].
 == Export Data to CSV File==
@@ Line 13: / Line 8: @@
 When there is lots of data (e.g. more than 100 000) rows, it's not feasible to show all data in a table in the UI, and that's why ChartView has a limitation of 10 000 rows by default. ChartView can still export more data (easily over 1 000 000 rows), because the row count is selected for the CSV export file separately.
 == Importing .XES Files ==
@@ Line 41: / Line 28: @@
 ** '''Id''': value will be converted into GUID
 ** Other values are converted into string using invariant culture
 [[Category: QPR ProcessAnalyzer]]

Ollvihe: /* Importing and Exporting .PACM Files */

2021-06-28T11:10:40Z

Importing and Exporting .PACM Files

← Older revision		Revision as of 11:10, 28 June 2021
Line 15:		Line 15:

	== Importing and Exporting .PACM Files==		== Importing and Exporting .PACM Files==
	QPR ProcessAnalyzer models can be exported into '''.pacm files''' (~~pacm=~~QPR ProcessAnalyzer compressed model file) ~~using~~ the ~~[[QPR_ProcessAnalyzer_Deployment_Package#Model_Manager\|Model Manager]]~~. Pacm files can be imported ~~to QPR ProcessAnalyzer~~ by ~~using~~ the ~~[[Importing_Data_to_QPR_ProcessAnalyzer\|Data import]] view~~.		QPR ProcessAnalyzer models can be exported into '''.pacm files''' (QPR ProcessAnalyzer compressed model file format) in the models list by clicking '''Export .pacm''' for a model. Pacm files can be imported as new models in the models list by hovering a project and in the menu selecting '''Import model from .pacm'''.

	~~One .pacm~~ file contains one model including case and event attributes and model specific user rights.		Pacm file contains one model including case and event attributes and model specific user rights. If importing a model from a .pacm file to the same database from which the model was exported, all data in the .pacm file is imported. If importing from a .pacm file to a different database than from which the model was exported, the following restrictions apply:

	If importing a model from a .pacm file to the same database from which the model was exported, all data in the .pacm file is imported. If importing from a .pacm file to a different database than from which the model was exported, the following restrictions apply:
	* Imported filters are restricted to those that were made by the user that exported the model.		* Imported filters are restricted to those that were made by the user that exported the model.
	* Model specific user rights are imported if the same UserID-Username combination exists in the target database.		* Model specific user rights are imported if the same UserID-Username combination exists in the target database.