Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I am currently importing vendors by data management in D365FO using the Vendors V2 entity and its take to long.
My data volume is 6 thousand vendors and it takes hours to import.
Have you had the same situations?
Did you enable "set based processing" on Vendor V2 data entity?
No, I didn't select the option set-based processing.
Then, if I tick this checkbox it means that d365 will import everything in one bunch? Does it insert in one SQL statement?
I know that it will remove the latency. However, it will not run the business logic to each line, won't it?
Yes, it will become bulk insert with set based enabled. If it needs to check business logic for each line then it shouldn't be enabled.
Besides set based processing , data management for importing runs single threaded by default.
To change this either go to System Administration --> Data Management --> Framework parameters --> Entity Settings --> Configure entity Execution parameters --> Select your entity --> Set import task count to a higher number (each task basically is a thread on your AOS).
This is from a parameter perspective, if parameterizing it is an issue you can execute this on the fly as well. To perform this on the fly select your import project and press run project, then on the import screen, disable the checkmark at Execute Target Step, and press import. This should initially validate and read the file, press view staging data now and click the copy data to target button at the top.
You will now see the number of records and the amount of tasks you will be running it with, change this to a number you like and press run (or run asynchronously).
Please note that increasing the tasks is not enabled for all types of data entities, but D365FO will give a warning if it is not possible.
When I have setup the entity execution parameters, the following message appeared:
"Custom sequence is defined for the entity 'Vendors V2' , more than one task is not supported"
Thank you in advance
Indeed, the Vendors V2 entity is not supported on the entity execution parameters. Can you tell what type of environment you are using and if you did run the import via the batch or was it started directly from the client? Using the batch will also improve some performance and it will run more stable.
Yes, I've run it directly from the client.
Now, I'm using the batch and I can see some performance improvements.
How to tell if the data entity is supported on the entity execution parameters?
Business Applications communities