Share
Report
3Hi,
We are looking to use Dataverse Virtual Tables to bring data from a SQL Server-based application into our Dataverse environment, in order to have this data available alongside our other business applications which are Dynamics 365-based.
Some of the entities/tables in the SQL Server-based application (e.g. a client record) duplicate the core tables available in the Dataverse (e.g. Account). Likewise, some of the fields/columns in the SQL Server-based application's tables duplicate the columns natively available within the Dataverse's tables.
What we are looking to do is keep the duplicated areas 'in sync' with one another. For example, if a user changes the client's first name in a D365-based app, change the first name of the same client in the SQL Server-based app. (Clients are served by multiple areas of the business, but different business areas use different apps, hence the need to keep them in sync).
If it were a single field, we could easily build a Power Automate flow along the lines of "if field X value changes in SQL Server-based app (i.e. in the virtual table), change field X value in Dataverse (i.e. native table)". However, we would need to do this in both directions (neither side could be made read-only), plus we'd need to do this across every duplicated field – there could be hundreds.
Is there a better way to keep this data in-sync across the native Dataverse tables and the virtual tables? (Or just across two native Dataverse tables for that matter!)
Thanks!
All responses (
Answers (
