Correct Statements About Dataverse Data Import and Integration

Correct Answers: A, C and E

Dataverse provides several tools to import and export data.

They include Data Import Wizard, Power Query, Power Automate, Dataflows, and others.

A Solution Architect always needs to assess when to bring data into the Dataverse or connect to an external data source.

Dataverse provides virtual table functionality for connection to the external data sources without importing data.

The model-driven app uses only the Dataverse as a data source, including the integration with external data.

For example, developers can embed a canvas app in a model-driven app.

Canvas apps can use any of the 300+ connectors that Power Platform provides.

A virtual table is another possibility to bring data from other systems into model-driven apps without data storing and replication in the Dataverse.

Option A is correct because users with appropriate table access can create and write data to the virtual table.

The records will be updated on the source data side in almost no time.

Option C is correct because users cannot enable field security for virtual tables.

This is because the virtual tables have organization ownership and do not support the record type security.

Also, the virtual table's columns cannot have calculated or rollup attributes.

These types of operations must be done on the external data side.

Option E is correct because the virtual table uses the GUID primary key from the external data entities for the Dataverse mapping purposes.

Option B is incorrect because model-driven apps can use only the Dataverse as a data source, including integrating with external data.

Option D is incorrect because all Dataverse API operations, including batch data import, are subject to the API entitlement and service protection limits.

For more information about the Dataverse import and virtual tables, please visit the below URLs:

The Dataverse data integration allows you to integrate data from external sources with the Dataverse environment. When designing a data integration, it is important to determine when to import data or connect to external data. Let's review the statements provided:

A. You can create and write data to virtual tables

This statement is true. Dataverse provides the capability to create virtual tables that can be used to represent data from external systems or other data sources. These virtual tables can be read from and written to just like any other table in Dataverse.

B. You can use custom connectors with model-driven apps

This statement is also true. Dataverse provides the capability to create custom connectors that can be used to connect to external systems or data sources. These connectors can be used with model-driven apps to provide access to external data.

C. You cannot enable field security for the virtual table

This statement is false. Field security can be enabled for virtual tables just like any other table in Dataverse. This allows you to control access to specific fields in the virtual table based on security roles.

D. You can batch import data without API limits

This statement is true. Dataverse provides the capability to import data in batches without any API limits. This can be done using the Data Import Wizard or through the use of code.

E. You map the virtual entities with the external entities using GUID primary key.

This statement is also true. When integrating data from external systems, you need to map the data in the external system to the data in Dataverse. This is done using the GUID primary key of the entities in both systems. This mapping allows you to ensure that the data in Dataverse is consistent with the data in the external system.

In summary, all of the statements provided in the question are either true or false. Dataverse provides the capability to create virtual tables, use custom connectors with model-driven apps, enable field security for virtual tables, import data in batches without API limits, and map virtual entities with external entities using GUID primary key.