Virtual Entities and Custom Connectors: A Comprehensive Overview

Correct Answers: B and D

Dataverse provides virtual entities for integration with external data.

A virtual entity is the metadata construct that brings data from other systems into model-driven apps without data storing and replication in the Dataverse.

The end-users do not see any difference when they work with virtual entities comparing to the other entities.

The virtual entity has a virtual data provider and an optional virtual entity data source.

Dataverse offers two data providers for virtual entities: OData v4 (the default provider) and Azure cosmos DB.

If there is no data provider for your external data source, you can create a custom virtual entity data provider.

The custom virtual data providers can support the data CRUD management by using registered plug-ins.

You do not need to create a step for each data operation.

You need to register a custom data provider using the Dataverse Plug-in Registration Tool that includes the Main Operation Event Handlers (Number 2) within the Data Provider registration screen (Number 1).

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

Developers can embed a canvas app in a model-driven app.

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

Virtual entities (or virtual tables) bring the model-driven apps integration capabilities with external data closer to canvas apps.

Option B is correct because you need to register the plug-in for CRUD operations for the virtual entity's data updates.

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

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

Option C is incorrect because the virtual entity cannot have calculated or rollup attributes.

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

For more information about the Dataverse virtual entities, please visit the below URLs:

Sure, I'd be happy to explain the answer to this question!

A. You can use custom connectors with model-driven apps This statement is correct. Custom connectors are used to connect external data sources to Power Apps and Power Automate. They allow you to create a connection to an API, such as a REST API, and use that data within your app. Custom connectors can be used with model-driven apps, which are a type of Power App that allow you to create rich, interactive experiences for data entry and viewing.

B. You can update data in the virtual entity using a registered plug-in This statement is also correct. Virtual entities are a type of entity in the Common Data Service that allow you to access data from an external system without actually storing that data in the Common Data Service. Virtual entities can be read-only, or you can use plug-ins to write data back to the external system. By registering a plug-in on the virtual entity, you can update data in the external system when the virtual entity is updated in the Common Data Service.

C. You can have a calculated attribute in the virtual entity This statement is also correct. Calculated attributes are used to perform calculations on fields in the Common Data Service. Virtual entities support calculated attributes, which means you can perform calculations on fields in the external system that the virtual entity is connected to.

D. You map the virtual entities with the external entities using GUID primary key. This statement is incorrect. When you create a virtual entity, you map it to an external data source by defining the properties of the virtual entity and the external data source. You do not necessarily use a GUID primary key for this mapping. The key that you use for mapping will depend on the structure of the external data source.

In summary, the correct statements about virtual entities and custom connectors in the context of a model-driven app that operates on data from external data sources are:

A. You can use custom connectors with model-driven apps B. You can update data in the virtual entity using a registered plug-in C. You can have a calculated attribute in the virtual entity

I hope that helps!