We load all of our large journals this way but I am currently in discussion with Microsoft (via a support ticket) because it takes way longer than I think it should when we try to import journals that are 10K-20K lines. It is taking 4+ hours for a 19K line journal, for example. The response I received from MS support initially was that we should break down the imports into smaller batches but I pushed back that this was not a solution, rather it was a workaround and not at all acceptable.Ā
If anyone has a different experience with this functionality, please let me know. While 20K lines is a lot of data, my expectation is that Dynamics should be able to handle in minutes, not hours.
—————————— Karl Arensdorf Corporate Controller Mansfield Oil Company Gainesville GA —————————— ——————————————-
Our experience varied somewhat but we’ve definitely loaded in 10k to 20k lines in under an hour. Anecdotally, any file that had a single error line (some of the data was invalid) took significantly longer to load in than a file with no errors. The entity being loaded into also affected that as the more validations required on the data the longer it took for the system to upload.
Please note:
This action will also remove this member from your connections and send a report to the site admin.
Please allow a few minutes for this process to complete.
Report
You have already reported this .
Welcome to our new site!
Here you will find a wealth of information created for peopleĀ that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!