From the Microsoft Dynamics 365 for Finance and Operations/AX Blogs: Performance Review; Containerization; Entity export; Async method

August 23 2019

In this week's Dynamics 365 for Finance & Operations (D365FO) and  AX blog roundup:

  • Looking into Dynamics 365 Performance Review
  • Dynamics 365 Finance and Operations containerization
  • D365FO Bring Your Own Database entity export failing with no error message
  • Calling async method from X++

Looking into Dynamics 365 Performance Review

On Dynamics 365 Finance and Operations and Dynamics AX in the Field blog, Megan Lenling stated that the D365FO Performance Review is an important part of Microsoft's offering. She noted that the feature offers users proactive support as well as insight and understanding of the health and performance of their deployments.

Lenling conducted a Q&A with senior D365FO PFE Rod Hansen to get answers to some common questions. In the blog post, Hansen explained exactly what a Performance Review is and talked about some of its functions.

You can read the Q&A and learn at what stages of a project it's most important to focus on performance, the benefits a customer can expect to gain from the Performance Review and more here.

D365FO containerization

On Galyna Fedorova's Microsoft Dynamics AX blog, Fedorova detailed the containerization process in D365.

Containerization, also called packing, is the process of using standardized containers for the storage and transport of units from a warehouse. When packing is performed it’s specified as part of the methods in the wave template. This setup affects the way in which containerization logic works.

In her blog post, Fedorova discussed the constraints that are evaluated during containerization, such as warehouse-specific constraints and container-specific constraints. She also explained the advantages offered by containerization.

You can learn about containerization in D365FO here.

D365FO  Bring Your Own Database entity export issues

On the Microsoft Dynamics D365FO Coding (AXCALATED) blog, Adam Chronister stated that recently after standing up a new export and going to export the sales order lines V2 and purchase order lines V2 entity's to Azure SQL Database, the export started to fail. But there wasn't an error noted in execution log.

After doing some digging, Chronister found the error message. However, it didn't offer any helpful information. It just noted that the entity was crashing. He tried to solve the issue a number of ways but nothing worked – he was still getting the same error. Chronister wrote:

However I deleted all fields within the mapping and just did a few base fields the entity index is based on and found that the entity would export. Because of this I knew that something was wrong with one of the field mappings.

You can find out what to do if you have an entity that's failing export here.

Calling async method from X++

On his Goshoom.NET Dev Blog, Martin Dráb stated that there's a trend in the .NET world to make time-consuming calls asynchronous, to stop applications from getting blocked when waiting for a response from a web service, for example.

Many existing APIs were enhanced with asynchronous variants of previously synchronous actions and some newer APIs offer only asynchronous methods. So . . . how can we call such asynchronous methods from X++?

In his blog post, Dráb explained how to do that. You can read about it here.

FREE Membership Required to View Full Content:

Become a MemberLogin
Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also have the option to receive periodic email newsletters with the latest relevant articles and content updates. Learn more about us here
About MSDW Reporter

More about MSDW Reporter