Data Sources for Power Apps Project

Correct Answers: B, C and E

For Power Platform projects, you should consider storing all data in the Dataverse.

The Dataverse provides not only the storage for various data types but also rich business logic, security, data, and integration functionality.

You can use the Dataverse API to access data in the Dataverse outside the Power Platform.

Or you can copy the data to the Dataverse from other sources.

If you need to use data from other sources in the Power Apps project, several tools will help you.

These tools include the Connectors, Virtual tables, and Dataflows.

Power Platform provides 400+ out-of-the-box connectors, including the SQL Server Connector.

This connector allows you to connect to Azure SQL Database and SQL Server running on-premises.

The Virtual table creates the representation of non-Dataverse data sources inside the Dataverse in a table form.

You can read and write the data in a virtual table, and the Dataverse takes care of the data synchronization.

The Dataflows help you extract, transform, and load (ETL) data from any source and bring it to the Dataverse or Azure Data Lake Storage.

Option A is incorrect because we need to create or use the Custom connector only if Microsoft does not provide the connector for the data source.

Microsoft offers the SQL Connector, and we do not need to create a custom connector.

Option D is incorrect because the activity table does not provide the data integration with non-Dataverse data sources.

Option F is incorrect because the SharePoint Connector is irrelevant for the current task.

For more information about the data source type for Power Platform projects, please visit the below URLs:

As a Solution Architect, you need to ensure that your Power Apps project can read and write data from both Azure SQL Database and Dataverse. To achieve this, you need to evaluate the data sources that can be used in your solution.

Here are the explanations of the data sources that you can use in your solution:

A. Custom Connector: Custom connectors allow you to connect to any web-based service that exposes an API. You can create a custom connector to connect to your Azure SQL Database and Dataverse. Custom connectors can be created using Azure Logic Apps or Power Automate.

B. Virtual table: Virtual tables are a feature of Dataverse that allows you to create a table that is based on the data from another table. Virtual tables do not store data themselves but provide a view of the data from another table. You can create a virtual table based on the data from your Azure SQL Database and use it in your Power Apps.

C. SQL Server Connector: The SQL Server Connector allows you to connect to an instance of Microsoft SQL Server or Azure SQL Database. You can use this connector to read and write data to your Azure SQL Database from your Power Apps.

D. Activity table: The activity table is a special type of table in Dataverse that tracks changes to other tables in the Dataverse. The activity table is automatically created when you create a table in Dataverse. You can use the activity table to track changes to your Azure SQL Database.

E. Dataflows: Dataflows allow you to transform and load data from multiple sources into Dataverse. You can use dataflows to load data from your Azure SQL Database into Dataverse.

F. SharePoint Connector: The SharePoint Connector allows you to connect to a SharePoint list or library. You can use this connector to read and write data to SharePoint from your Power Apps. However, this connector cannot be used to connect to Azure SQL Database or Dataverse.

Therefore, the three data sources that you can use in your solution are:

1. Custom Connector
2. Virtual table
3. SQL Server Connector

Using these data sources, you can connect your Power Apps to your Azure SQL Database and Dataverse and read and write data from both sources.