Microsoft Dynamics 365
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Business Central Team
The process should upload the file from the local PC before it does anything and then process the file once it is in the tenant. IT needs to continue processing the file even if the user disconnects.
If you need to import a file you have to make sure the client stays connected . If this a large file it can take many hours and can sometimes run over night.
I'm in the same boat. I need to import 65000 items. This is absolutely not that many for a wholesaler. The way I'm doing it: I open a remote desktop connection to a server (as that computer never shuts down). There I start the import and let it run the entire night. In the morning I hope not a single error occurred and everything is imported after hours of running. But reality is that the system loads for minutes/hours, than you need to click a confirm button, on which it loads for hours again, than you have package records (with or without errors), than you need to "validate" and wait again for hours, than sometimes you get package errors that didn't show up in the previous phase, so you need to correct them, and apply, than wait again for hours,...☹
With customer import, when I leave all data validations on, I need to be there to click on "yes" or "no" everytime I get a prompt for a specific record if the VAT-number got recognized and the system asks me to take over the name and address field... I can't set my answer upfront and just let it run uninterrupted. ☹
Please foresee also a button where you can disable validation for all (non-primary key / including) -fields.
I fully agree, rapidstart import becomes slower and slower with each version. Due to this reason the developers need to make temporary imports for getting items and item balances inside BC. If it takes rapidstart to process this data several hours, then for temporary tools it is just a couple of minutes to get 50 000 items inside.
I agree, I recently had an Items import with 50,000 records to create this took over 5hrs, and into cloud this just isn't possible as the system drop due to inactivity, client needs a refresh etc!
In the end I have to reduce the number of records down and run this import over a number of files! not ideal.