Since Dynamics 365 for Finance and Operations version 10.0.12 we’ve been able to use FnO (public) data entities as CDS Virtual Entities. This will allow us to create model-driven Power Apps for Finance and Operations entities without having to copy data between Finance and Operations and the Common Data Service (CDS). This opens a lot of scenarios and new ways of integrating MSDyn365FO with Customer Engagement.
If you want to learn more about setting up the Virtual Entities for FnO you can:
Read this blog post from Aurélien Clere where he describes all the steps and you’ll be able to find more information about CDS integrations with Finance and Operations.
After waiting for it for a long time it’s here! If any of your customers has self-service sandbox environments you’ve been doing this by hand. We’ve been on self-service for over a year and a half with a customer, since the private preview, and we’ve REALLY missed this feature in Azure DevOps.
Some time ago I published the first version of ISV License Generator to help us generate a license for a Microsoft Dynamics 365 for Finance and Operations ISV solution, using a CSP cryptographic USB token instead of a software certificate.
With the new ISV License Generator version 0.2 I’ve implemented support for SHA-2/SHA-256 while keeping support for SHA-1 until it’s deprecated.
It’s one of the most common requirements from a customer: the need to integrate Dynamics 365 with other systems. With the (back in the day) new AX7 we got a new way of integrating using the OData REST endpoint and the exposed Data Entities.
But integrations using the OData endpoints have low performance and for high-volume integrations it’s better to use the Data management package REST API. A (not so) high volume usage of the OData REST API will translate into performance issues.
If you’re working with the (not so) new self-service Tier 2 environments in Dynamics 365 for Finance and Operations you might have already noticed this: the reports in Tier 2+ and production environments aren’t using the SSRS report viewer, instead they’re being displayed in a beautiful PDF preview form.
But what happens on your development box?
If you want to know more about self-service environments you can read these posts I wrote a while back:
Before the SysOperation Framework was introduced in AX2012, we used the RunBase Framework, and maybe doing these things looked easier/quickier with RunBase because all the logic was in a single class. But in the end what we need to do is practically the same but we have to do it in the UIBuilder class.
Let me show you and explain all the code. I’ll only show the DataContract and UIBuilder classes as they’re the only important ones in this case.
This is another post about solving Dynamics 365 problems using external tools. However I’m starting to think as everything Azure-related as not external at all. In this case I’ll show different scenarios using Azure functions with Dynamics 365.
I’m sorry for my English-speaking readers because, maybe, this post will be a bit useless for you as all the content I’ll talk about is in Spanish. But it’s always good to know!
In the last few days I’ve taken part in a community event, the 365 Saturday online, and I’ve also started a podcast. I want to talk a bit about this.
Dynamics Power Spain Online 2020
This has been my fourth participation as a speaker in the last three years and as usual I’ve presented a session with Juanan. This time we’ve talked about using Azure DevOps with Microsoft Dynamics 365 for Finance and Operations.
It’s a topic I write about a lot, but we really think there’s still many people using it in a wrong way or just using the source control part. And that’s bad!
I’ve written this post after Mötz Jensen asked to in a long and really interesting Twitter discussion on branching and version control in Dynamics 365 for Finance and Operations. This is Denis Trunin‘s tweet that initiated it all:
New blog post – Understanding D365FO Version control system and why it is different from AX2012 https://t.co/S26JU99qtP