Dynamics 365 for Finance and Operations version 8.1.3 – PU23 – new features

January 20th, 2019 by Stephen Jones Leave a reply »

This version will be released in January 2019 and has an actual build number of 8.1.227. It includes platform update 23.

For the many Extensibility changes in Dynamics 365 for Finance and Operations version 8.1.3 see https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/extensibility/extensibility-changes-813

Collection letters
Set up collection letters by customer,, so that the collection letter code for each transaction is tracked, but the collection letter processing is based on a single collection letter level that is stored for the customer.

Settle remainder
To settle the amount remaining from settlement activity by applying that amount to a ledger account or to another customer. Settle the remainder either when you are settling amounts entered into a journal, or when settling open transactions.

Electronic reporting:
• Import from files in JSON format. You can now configure an Electronic reporting (ER) format to parse incoming files in JSON format. You can then set up ER mappings that specify how information from JSON files is used to update application data.
• Support country context-specific ER model mappings. To isolate country-specific logic of data access in a single ER model mapping.
o Specify a country context for ER model mapping.
o Manage multiple country-specific mappings for a single ER data model.
o Depending on the legal entity’s primary address, the appropriate country/region-specific model mapping will be used when an ER format is used to generate an electronic document.

There are also some Russian localisations for AR AP movement registers that may be worth checking.

Platform 23 update features:
Legal entity filtering using grid column headers
For grids with cross-company queries, users can filter the Legal entity column using the column drop-down menu, similar to other columns in the grid. A user looking at the global transactions for a specific customer, can find the transactions within a small subset of companies. Prior to this feature, he would have had to filter using the Customer range tab on the Advanced filter or sort dialog box, or utilize page-specific custom filters.

Export to Excel
In Platform update 22, the Export to Excel feature was improved to allow users to export up to 1 million rows from a grid in Finance and Operations, a substantial increase from the previous 10,000-row limit. In Platform update 23, after the export completes, users will receive a notification in the Action center that the export has finished. The notification includes a link to download the Excel file containing the exported data. The link and notification are accessible for approximately three days after the export completes.

Manage access to network printers across legal entities

System network printers management form. System Administrators can use this, along with the Document Routing Agent (DRA) to register network printers with Dynamics 365 for Finance and Operations. When you enable this feature, a Preview link will appear on the System network printers form (Organization administration > Setup > Network printers and click System network printers). After you register the network printers with the service using the DRA, you will see the configuration information for each legal entity in the organization.

Enabling index hints in X++
Microsoft Dynamics AX 2009 and earlier versions supported INDEX HINTS from X++. However, this was deprecated when Dynamics AX 2012 was released. A reason why this was deprecated is because a misguided index hit could damage the queries. However, thousands of queries in hundreds of tenants shows that SQL may come up with less optimal plans for simple queries, Finance and Operations has thus brought back X++ hints. However, X++ hints should still only be used with extreme caution. Use Index hints sparingly, and only when you can ensure that it causes more benefit than harm. When in doubt, avoid using index hints. A new API is added on common allowIndexHint with a default behavior of False. This allows developers to opt-in and explicitly enable index hint. The old syntax on the select statement for specifying index hint is reused.For an existing X++ code that specifies index hint, there is no change to the current behavior until the new API is invoked.

Automated refresh of Entity store (opt-in)
Let the system manage Entity store refresh instead of scheduling the refresh yourself. When enabled, choose a refresh pattern (hourly, twice a day, daily, or weekly). When specified, the system keeps the entity store updated for the selected pattern. The system will also switch to the new update form, where you will be notified with a status and possible refresh issues.

Entity store as a Data Lake (preview)
In Platform update 23, you can select to use Entity store as a Data Lake. When this feature is turned on, Entity store data isn’t populated in the relational Entity store database in the Microsoft subscription. Instead, it’s populated in an Azure Data Lake Storage Gen2 account in your own subscription. You can use the full capabilities of PowerBI.com and other Azure tools to work with Entity store.

For more information: contact Synergy Software Systems, Dubai based since 1991 and Dynamics Partner since 2003.


Comments are closed.