Dynamics 365 for Finance and

In combination with Office 2016, it is possible to evaluate and adjust transaction data and master data directly in Excel. In earlier versions, this was…

In combination with Office 2016, it is possible to evaluate and adjust transaction data and master data directly in Excel. In earlier versions, this was much more cumbersome or only possible with the help of additional tools. In many forms, a link to Excel is highlighted via the menu bar or an icon at the edge of the screen. This way, a posting journal can be created in the ERP and then filled in Excel with data from another source with little effort (copy/paste). Fast data entry, as known from the earlier AX versions, is thus also possible in the cloud. The displayed columns and the appearance are adapted to the respective needs. A simple designer is also included. Via an add-in that starts automatically with Excel, the data can be loaded from the ERP (Refresh) or written back (Publish). Journals with up to 10’000 lines can be edited just as easily. In Excel there is even a preview of possible values (account numbers / dimensions / currencies / …) just as you know them from the forms. Only a jump to the main table is still missing :-> If at some point the payment terms, customer master data, account master or even the item master need to be adjusted, this is a simple way to do it. Permissions and dependencies to other, linked tables are also monitored and ensured via the DMF (Data Management Framework). The DMF also provides various applications with access to the data in the ERP. This way, files can also be imported or exported in an automated manner. The well-known «Export to Excel» function is also available for exporting data in tabular form. Of course, Microsoft Word has not been forgotten either! With the same add-in / logic, templates can likewise be enriched with ERP data. As an example, I can see here an item specification or the data sheet of a machine. The data from the various areas is exported as an «entity». An entity represents a grouping of different fields that are processed together. For a GL journal, these would include: journal number, line n