As a developer, I built multiple integrations with Dataverse using Azure Functions. Historically, XrmTooling (the firstparty library to perform operations with Dataverse) is .Net Framework based, so to leverage this Package I had to use V1 Azure Functions. Microsoft released .Net Core version of the tooling for a public preview so at the moment it’s …
The post Migrate Azure Functions from…
Continue Reading Andrew Butenko’s Article on their blog
Migrate Azure Functions from .Net Framework (v1) to .Net Core (v3) – Andrew Butenko’s Blog
As a developer, I built multiple integrations with Dataverse using Azure Functions. Historically, XrmTooling (the firstparty library to perform operations with Dataverse) is .Net Framework based, so to leverage this Package I had to use V1 Azure Functions. Microsoft released .Net Core version of the tooling for a public preview so at the moment it’s …
Blog Syndicated with Andrew Butenko’s Permission
More About This Author
Array
- Dyn365CE1 April 2024Canvas Apps: Watch PCF Component
- Dyn365CE6 November 2023Dataverse “When an action is performed” trigger doesn’t fire – what to do
- Dyn365CE10 October 2023Synchronizing aggregation fields and subgrids data in MDA forms
- Dyn365CE28 September 2023Validating current user privileges on the client side