From the Microsoft Dynamics 365/AX Blogs: Connect to BYOD; Custom table; Reporting; Purchase order prepayments

This week on the Microsoft Dynamics 365 and AX blog roundup:

• Dynamics 365 for Operations: Connect to BYOD (Azure SQL) using X++ code
• How to create a custom table to use as a ledger financial dimension - Dynamics 365 for Finance and Operations
• Dynamics AX 2012 reporting: Error "client found response content type of," but expected "text/xml" when running a report based on cubes
• Purchase order prepayments

Dynamics 365 for Operations: connect to BYOD (Azure SQL) using X++ code

On his Dynamics 365 for Finance and Operations Enterprise Edition with Sukrut blog, Sukrut Parab said that D365FO lets you export data entities to your own Microsoft Azure SQL database. This feature is also known as bring your own database (BYOD).

Analytics teams use BYOD extensively for different financial reports, but sometimes the data on those reports doesn't tally to AX, he said.

So Parab wrote code to verify the record count between the AX table, and the table for the published entity in BYOD and then set it up to notify the admin if there's any mismatch.

You can utilize this in batch job to send alerts if you find any mismatch. If publish job fails there is no way Dynamics 365 for Operations notifies you automatically unless you go and check your configured data projects.

You can find the code here.

How to create a custom table to use as a ledger financial dimension - Dynamics 365 for Finance and Operations

On his ShabibAX blog, Shabib Raza said that one of his company's Dynamics 365 clients needed to ...