I previously wrote a couple of blog posts (post1 and post2) suggesting two different ways to access your Dataverse metadata in Synapse. Both of these techniques are now redundant as Microsoft announced in May 2022 that the Dataverse metadata is now available directly in Synapse. Your Synapse serverless pool now contains additional external tables with the metadata. Your queries … [Read more...] about Synapse Link for Dataverse – Metadata
Azure
Microsoft Azure is a public cloud computing platform and provides a range of cloud computing services such Platform as a Service (PaaS), Infrastructure as a Service (IaaS) and Software as a Service (SaaS). There are many benefits to using Azure as it's perfect for small businesses, security and compliance and compliments your current IT structure. Check out the latest posts from Joe Gill from tutorials to the latest news.
Dataverse Metadata in Synapse
Note: the Dataverse metadata is now available out of the box and so this approach is no longer relevant. I have an updated post here When you configure Synapse Link for Dataverse it exports your Dataverse data into a Synapse data lake as CSV files. A database with external tables is created automatically in the Serverless SQL pool providing access to the data in the CSV … [Read more...] about Dataverse Metadata in Synapse
Synapse Link for Dataverse – Option Sets
Note: the Dataverse metadata is now available out of the box and so this approach is no longer relevant. I have an updated post here On November 23 Microsft announced that DES (Data Export Services) will be deprecated and will reach end of life in November 2022. Microsoft is recommending that customers use Azure Synapse Link for Dataverse instead. DES has been around for a … [Read more...] about Synapse Link for Dataverse – Option Sets
Track Issues in Flows and Logic Apps using Correlation Id
Previously I have written some blog post, like this one, showing how easy it is to create API endpoints in Flow and Logic Apps. This involves creating a workflow that gets triggered by an Http Request with a Json payload. There are asynchronous “fire and forget” API calls and the calling process receives a 202 response code to indicate the workflow has been triggered. … [Read more...] about Track Issues in Flows and Logic Apps using Correlation Id
Flow – Http Request – Split On Collection
A use case I like with to use with Flow and Logic Apps is to create a workflow triggered by a Http Request that acts as an API endpoint. In a previous post I explained how to do it and how to configure Flow to the validate the Json payload. In that post the Json request was just a simple contact object with a few data fields that we inserted into Dynamics 365. Did know … [Read more...] about Flow – Http Request – Split On Collection
