114
When we export large data from Dynamics 365 Operations to an excel, the data is not copied completely and is restricted to 2000 rows only. We have to export the remaining rows once again to the excel to get the whole data. It will be good, if there is no such restriction and the data can be exported to an excel completely at a time.
STATUS DETAILS
Under Review

Comments

M

Please find a solution to export a far larger number of transctions.

Category: Reporting and Analytics

M

We really need to find a way to export way larger files. We have an implementation with > 1.000.000 ledger transactions per week. Lots of invoices and other tranactions. The 10 K limit is way to low and cannot be explained to customers. Please find a solution to export a far larger number of transctions.

Category: Reporting and Analytics

M

My client just asked for this feature on the project posted transactions inquiry page - ability to exceed 10000.   In the general ledger accounting source explorer there is a convenient button that is not limited to 10,000 rows.   We would like this button in more places such as the posted project transactions inquiry page if an overall removal of the limitation cannot happen.

Category: Reporting and Analytics

M

I can see in Platform Update 7 (May 2017) release as below


(https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/get-started/whats-new-platform-update-7)


"The static Export to Excel limit has been increased from 2k to 10k to allow more rows to be exported from a grid. If there is an entity representing the data in the grid we recommended that you use Open in Excel and the Excel Add-in instead, since there is no hard row limit. In addition, if there is an entity and the user has admin privileges then DIXF (data management) is also an option"


Thank you for it. But there are requirements to import even more than that 10k records.


I hope it will be incorporated in the next release.

Category: Reporting and Analytics

M

El proceso de poder exportar a Excel desde un Form de Pantalla es porque se tienen la posibilidad de agregar campos nuevos o ocupar para exportar la información que se requiere y desde un reporte al exportarlo a Excel no se tiene la funcionalidad de ocultar campos.


 

Category: Reporting and Analytics

M

@Warren we do have about 2000 Data Entities, and you can easily create more. I think what you are describing is 100% possible as for now. 

Category: Reporting and Analytics

M

It would be nice to have more data entities even if they are read only that way we could have spreadsheets and BI tools directly linking to the data.

Category: Reporting and Analytics

M

Does this also happens when you export using the Data Entity framework? Perhaps if you export it first as CSV may work. 

Category: Reporting and Analytics

M

We are often working with 2,000+ rows of data.  Especially project data.  Especially from Project Posted Transactions.  Users are frustrated when they go to export their data and only get records up to 2,000 rows.  Can you somehow "hijack" your Data Management utility (which can export many more rows) to allow users to export the data they need.  Currently, it is trapped in AX for many users.

Category: Reporting and Analytics