The year 2021 has almost come to an end, and it’s time to review the changes we’ve had this past year.
So in case you’ve missed something, I hope you can find it here, although I won’t include all new or changed Dynamics 365 Finance & Operations features, only some of them, the ones I’ve found more interesting.
In January, we finally got something some of us had been waiting for a lot of time: Azure Pipelines task for asset deployment support fort self-service environments. With self-service environments being the default topology, more and more people were asking for this.
Visual Studio 2015 was the first IDE we used when AX7 was released back in 2016. We’ve been together a long time, and in February we said goodbye to it.
With this feature we can manually set sending limits for email providers that aren’t Microsoft 365, and if we’re using a Microsoft 365 provider the limit will be set automatically. You can read more here: Configure and send email.
In the April release, we got a new default IDE version and started working with Visual Studio 2017!
Another interesting feature that triggers business events when a batch is started, completed, failed or cancelled. For more information, see Batch business events.
In May we got an additional NuGet file after the Application Suite was split in two due to its growing size going over 500MB. This required of some tweaking of the build pipeline. Read more: Extra NuGet file requires manual update to hosted Azure DevOps build pipeline.
We also got a new setting for our batch jobs. In case there’s a database connection issue, instead of terminating the job, we can retry it. To do this, you need to implement the BatchRetriable interface in your controller class.
A real enhancement to be able to use more than one company with an embedded Power App! For more information, see Embed canvas apps from Power Apps.
What this really means is that we’re no longer able to do some SQL actions from LCS, and also that Finance and Operations is one step closer to a SaaS offering. We’re on the same service as our CRM/Power Platform colleagues now. You can learn more about the Data Administration and Management System (DAMS) reading this blog post.
In October, we also got official support for Visual Studio 2019! Learn more about the Dynamics 365 development tools in Visual Studio.
Another useful feature that we can use from the Power Platform. With this feature, we’ll be able to queue batch jobs that are in a terminal state using OData actions.
And at the end of the year we got something we’d been waiting for a long, long time: the general availability of the export to Azure Data Lake feature! Read the announcement here.
The first one is Internet Explorer 11 support for Dynamics 365 deprecattion.
The other one is that the add-in in Visual Studio no longer allows us to apply metadata hotfixes. Something from the prehistory of Dynamics 365 F&O, when One Version didn’t even exist and we had to apply hotfixes one by one, and by hand.
I don’t know you, but I HATED Enterprise Portal with all my heart. Not that we could use it or even needed it now that our ERP is web-based, but happy to see it gone forever.
The batch job to handle SQL index defragmentation was stopped and is not necessary anymore as Microsoft is doing it.
This has been a hard one, in my opinion. Two tools we had in LCS to monitor our production environments were gone: Microsoft Azure SQL reports in Lifecycle Services (LCS) and Azure SQL actions in LCS.
This is related to the DAMS feature I explained before and if your prod environment has performance issues you need to open a support request.
And that’s all. What will 2022 bring to the #XppGroupies? No idea at all, we need to wait for the April release notes to see new features and the roadmap.
But we have something! Some improvements to developer performance will come in Platform Update 49, you can read it at Peter Villadsen’s blog here.