Virtual table: Difference between revisions

Revision as of 15:00, 13 July 2023

Dataverse/Dynamics
Resco Suite Resco Field Service+ Resco Inspections on Dynamics 365 Upgrading Microsoft Dynamics Business Process Flows File columns Virtual tables Resco CRM sync Maintain auditing records Sync plugins Duplicate detection XrmToolBox

Virtual tables (also known as virtual entities) enable the integration of data residing in external systems by seamlessly representing that data as tables in Microsoft Dataverse, without replication of data and often without custom coding^{(Microsoft documentation)}.

Since release 16.0, virtual tables can also be used in Resco mobile apps, both online and offline.

Preview Since release 16.1, users of the mobile apps can create, update, and delete records for these tables.

Configuration in Woodford

Virtual tables can be made available in the app projects using Woodford, just like standard tables.

Edit an app project in Woodford.
Select the virtual table from the Project menu.
Click Enable to add the table to your project.
Select the fields that you want to include.
Save all changes.

Synchronization

Most tables use "versionnumber" for incremental synchronization. Unfortunately, virtual tables don't have this column. As a fallback, we can use the "modifiedon" column instead. It must be properly configured in Woodford.

Preview If the table has a column that behaves as "modifiedon", we support create, update, and delete operations on this table, as well as incremental sync. The standard conflict resolution behavior applies.

Without this column, the only supported synchronization strategy is full sync. The table is read-only in the app.

Performance

The performance of virtual tables can be somewhat lower than standard tables. Dataverse acts only as the middle man and the performance mostly depends on the original data source.

Moreover, synchronization can be slower. The fetch for retrieving changed records differs for virtual tables. We have to read the changed records one by one.

{{#CI form: title = Was this information helpful? How can we improve? | type = inputs | [textarea] }}

@@ Line 1: / Line 1: @@
-{{Dynamics TOC}} {{WIP}}
+{{Dynamics TOC}}
 Virtual tables (also known as virtual entities) enable the integration of data residing in external systems by seamlessly representing that data as tables in Microsoft Dataverse, without replication of data and often without custom coding<sup>([https://learn.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve Microsoft documentation])</sup>.
-Since [[Releases/Spring 2023|release 16.0]], virtual entities can also be used in Resco mobile apps, both online and offline. By default, they use full sync, but if you select a proper '''Modified On Field''', you can enable different sync strategies. They remain read-only.
+Since [[Releases/Spring 2023|release 16.0]], virtual tables can also be used in [[Resco mobile apps]], both online and offline. {{Preview|Since [[Releases/Summer 2023|release 16.1]], users of the mobile apps can create, update, and delete records for these tables.}}
+== Configuration in Woodford ==
+Virtual tables can be made available in the app projects using Woodford, [[App_projects#Managing_entities|just like standard tables]].
+# Edit an app project in Woodford.
+# Select the virtual table from the '''Project''' menu.
+# Click '''Enable''' to add the table to your project.
+# Select the fields that you want to include.
+# Save all changes.
+=== Synchronization ===
+Most tables use "versionnumber" for incremental synchronization. Unfortunately, virtual tables don't have this column. As a fallback, we can use the "modifiedon" column instead. It must be properly configured in Woodford.
 [[File:Virtual entities in Woodford.png|600px]]
+{{Preview|If the table has a column that behaves as "modifiedon", we support create, update, and delete operations on this table, as well as incremental sync. The standard [[conflict resolution]] behavior applies.}}
+Without this column, the only supported synchronization strategy is full sync. The table is read-only in the app.
+== Performance ==
+The performance of virtual tables can be somewhat lower than standard tables. Dataverse acts only as the middle man and the performance mostly depends on the original data source.
+Moreover, synchronization can be slower. The fetch for retrieving changed records differs for virtual tables. We have to read the changed records one by one.
+{{Feedback}}
+[[Category:Dynamics]]