In Microsoft Dynamics 365 for Finance and Operations we can execute the CRUD operations from code in two different ways, record-per-record or set-based. Microsoft’s recommendation is to always use set-based operations, if possible, as you can check on the Implementation Best Practices for Dynamics 365: Performance best practices for a successful Dynamics 365 Finance and Operations implementation session from last June’s Business Applications Summit. Why? Set-based Vs. Record-per-record When we run a query in MSDyn365FO…
WARNING! THIS POST IS LONG OUTDATED AND VISUAL STUDIO 2019 IS THE DEFAULT IDE SINCE DYNAMICS 365 FINANCE AND OPERATIONS VERSION 10.0.21 AND THE VHD SINCE OCTOBER 2021 RELEASE. Tired of developing in Visual Studio 2015? You feel you’ve been left and forgotten in the past? Worry no more, you can use Visual Studio 2017/2019 to develop Microsoft Dynamics 365 for Finance & Operations! What are the advantages? Absolutely none at all! Visual Studio will…
READ THIS!!! This is a really old and outdated post. Microsoft is already offering native built-in monitoring and telemetry using Application Insights for Dynamics 365 F&O. You can learn more in this Learn article: Monitoring and telemetry using Application Insights. First of all… DISCLAIMER: think twice before using this on a productive environment. Then think again. And if you finally decide to use it, do it in the most cautious and light way. Why does…
One of the options to integrate MSDyn365FO with external systems is using the data entities with REST services and OData. To use OData the entity must have its IsPublic property set to Yes: Otherwise, if it´s an standard entity, we´ll need to duplicate it because it´s not possible to change the property value in an extension. If we´re doing an integration with an external system using OData to create new records in the ERP, we…
You can read my complete guide on Microsoft Dynamics 365 for Finance & Operations and Azure DevOps. In the first part of this post I wrote about Azure DevOps value and how to set it up in MSDyn365FO. I want to start this second part with a little rant. As I said in the first part, those who have been working with AX for several years were used to not using version-control systems. MSDyn365FO has…
You can read my complete guide on Microsoft Dynamics 365 for Finance & Operations and Azure DevOps. One of the major changes we got with Dynamics 365 has been the mandatory use of a source control system. In older versions, we had MorphX VCS for AX 2009 and the option to use TFS in AX 2009 and AX 2012, but it wasn’t mandatory. Actually, always from my experience, I think most of the projects used no…
There’s no mystery here but a misperception. Recently, a colleague found a little issue when using an AOT query to feed a view with a range dynamically filtered using a SysQueryRangeUtil method. Recreating the issue The query is pretty simple, only showing ledger transaction data from the GeneralJournalEntry and GeneralJournalAccountEntry tables. A range in the Ledger field from the current company was added as you can see in the pic below: We created a new range method by extending…
You can read my complete guide on Microsoft Dynamics 365 for Finance & Operations and Azure DevOps. Let’s go… Some weeks ago, the release pipeline extension for #MSDyn365FO was published in Azure DevOps Marketplace, taking us closer to the continuous integration scenario. While we wait for the official documentation we can check the notes on the announcement, and I’ve written a step by step guide to set it up on our projects. To configure the…