15
Need to be able to see all errors with the error description vs one at a time and copy or send to excel.
It is very inefficient for the user to have to see each error detail individually and then try to resolve.
In on-premise we are able to remove the record filter when we view the error to see all errors fro a particular table or even for a package or even all errors for all packages. We can then past to excel. This is very useful as then the user can resolve many errors at once (via data mapping, validation changes, adding supporting date, etc.).
I have a work around where I create a rapid start package and add table 8617 Config Package Error table and then I can export this to excel to see all the errors.
It is very inefficient for the user to have to see each error detail individually and then try to resolve.
In on-premise we are able to remove the record filter when we view the error to see all errors fro a particular table or even for a package or even all errors for all packages. We can then past to excel. This is very useful as then the user can resolve many errors at once (via data mapping, validation changes, adding supporting date, etc.).
I have a work around where I create a rapid start package and add table 8617 Config Package Error table and then I can export this to excel to see all the errors.
STATUS DETAILS
Completed
Comments
My work around for this for now is to add a package with table 8617 and export that to excel. You can at least get all the errors in one file to review
Category: Data Migrations
Business Central Team (administrator)