• Ad-hoc Creation Of Synapse Link Incremental Update Snapshot.

    At the moment, Dataverse 'Incremental Update' Dataverse snapshots are created to a strict time schedule, configured when then synapse link is setup.


    Also, snapshots are also only created (and able to be consumed) upon the arrival of new data, so old data can be handing around in a snapshot until new data arrives.


    There are legitimate use-cases to manually stipulate a point of time for a snapshot creation, namely:

    • Gathering of data at an arbitrary timepoint determined by an extraneous process, e.g. batch / scheduled processes.
    • Forcing a cut of data at a time where new data is not arriving.
    • Reducing cloud costs associated with ADF pipeline dataflows (explicit snapshot creation reduces the required frequency of the dataverse update, and inherent use of Integration Runtime cores).


  • Allow external access to Dataverse Sync Table 'Status'

    After setting up an Azure Synapse link, we can view the Sync status of each table through the 'Azure Synapse Link' page.


    If there is a failure to sync one of the tables, this is reported on the UI, but as far as I can see is not alerted elsewhere.


    Access to this status programmatically, or via exposed logs, would be useful for holistic reporting in tooling external to the Powerapps dataverse.




  • Ability to change Dataverse Synapse Link Sync time without having to fully reconfigure Synapse Link

    If we require to change the interval at which the Synapse Link syncs data to the data lake, we must destroy the the Synapse link and recreate it from scratch.


    We then must take steps to reconfigure any dependent systems. For example if we have setup a 'Copy Dataverse To SQL' ADF pipeline, we must configure the event trigger, and ensure syncs to the Azure SQL DB continue working.