This post will inform you about the Entity execution parameters which can be found on the Data import/export framework parameters form. It will give you an option for gaining performance when importing large number of records using the data management features.
Entity execution parameters
The entity execution parameters do have an option to provide information how to divide the workload when performing data import using the batch framework. In Microsoft Dynamics AX 2012 we were used to specify the number of tasks when creating the processing group. In the current product it can be defined in upfront as a parameter.
Use the next path to open the Entity execution parameters: System administration > Workspaces > Data management; Then click the Framework Parameters tile. The Data management workspace can also be started from your default dashboard.
On the Framework parameters form you can select the tab page Entity settings and the button Configure entity execution parameters to open the next form.
As you can see in the picture above, you can specify a threshold per entity when the tasks need to be split and how many tasks will be created then. You can also make variations for the same entity. So, you can use 4 tasks for smaller and 8 tasks for larger files.
When specifying these parameters with a task count, it will create multiple threads where the workload will be divided and run in parallel. From my experience, this can make a huge difference in performance during data import.
Import in batch
To be able to really use these settings, you have to run the import using the batch framework. The Import button on the Import project form, will start a single thread on the server. You can use the Import in batch button on the Import options menu.
Then complete the parameters on the batch slider to have the batch scheduled. When the batch job is executing, you can actually monitor how many tasks are created on the View tasks form. From the Execution details, you have a link to the batch job. On this form, you can browse deeper into the tasks for this job.
Good to know….
Some data entities like Fixed Assets, are not created to support the use of multiple tasks. When trying to setup these entities, you get an error like shown in the screenshot below.
That’s all for now. Till next time!
Microsoft Dynamics CommunitySubscribe to this blogger RSS FeedMy book on Merging global address book records in AX 2012
The post Speed up data import with (data) entity execution parameters appeared first on Kaya Consulting.
*This post is locked for comments