A short one for today! I stumbled upon this while configuring the new Azure Synapse Link for Dataverse feature for an environment. Most of the time, when I’m configuring resources
A short one for today! I stumbled upon this while configuring the new Azure Synapse Link for Dataverse feature for an environment. Most of the time, when I’m configuring resources
Recently for some of our Dataverse environments, we found duplicate records getting created (same GUID) for Notes and Work Order Incident tables in the corresponding CSV files. Here we were
I was recently helping my colleague Ebba Linnea Nilsson with a support ticket with data not being propagated correctly from dataverse to a datalake via Azure Synapse Link. It turned
Once you have configured Synapse Link for Dataverse you are likely to want to give your data consumers access to read the Dataverse data from Synapse. This post covers how
By default Synapse for Dataverse exports records as in-place updates so if the record already exists it gets updated and if not it gets created. This can be configured so