Data Export inventory setup

Dataflow Setup

You can set up dataflows to retrieve your inventory from Data Export.

If your inventory is coming from Data Export, you can configure dataflows as part of the setup.

Important

• Only complete the steps in this artcle if you configured Data Export as the mechanism for inventory and telemetry.
• When you see data in your storage account set up to receive data from Data Export, then use the Data Export configuration steps in this article. This configuration might show up to five days from the initial setup of Data Export in the Power Platform admin center.

Copy Azure Storage account URL

1. Navigate to the Azure portal.
2. Search for or select the storage account configured to receive Data Export data.
3. Select Endpoints.
4. Copy the Data Lake Storage URL to a text editor such as Notepad.
5. Append /powerplatform to the URL.

Confirm Storage Account permission

1. Navigate to the Azure portal.
2. Search for and select the storage account configured to receive Data Export data.
3. Select Access Control (IAM).
4. Select View my access.
5. Confirm you have the Storage Blob Data Reader role assigned.

Copy Environment Web API endpoint

1. Navigate to make.powerapps.com.
2. Select the environment with the CoE Starter Kit.
3. Select the Settings icon, then select Developer resources.
4. Copy the Web API endpoint.

Configure connections to data sources

1. Navigate to make.powerapps.com.
2. Select the environment with the CoE Starter Kit.
3. Select Dataflows.
4. Edit the CoE BYODL Makers dataflow.
5. Update the DatalakeURL parameter with the link to your Data Lake Storage URL and the EnvironmentAPI parameter with the link to your Environment Web API endpoint.
   1. Select each table shown in the Queries section and configure the connection.
   2. For each connection, select Organizational account and sign in.
   3. Once all connections are configured and there are no more warnings, select Next.
   4. Select the Makers table and confirm that this table is configured to load data to the existing admin_Maker table.

      Note

      If the table is configured to map to a new table or you don't see a mapping configured between source and destination columns, select Cancel and start again.

   5. Select Publish. Don't change any data mapping configuration.
   6. The CoE BYODL Makers start refreshing. Wait for the refresh to finish.
6. Edit the CoE BYODL Environments dataflow. Complete the same steps to update the DatalakeURL and EnvironmentAPI parameters and configure the connections to the data sources used by this dataflow.
7. Select Next.
8. Select the Environments table and confirm this table is configured to load data to the existing admin_Environment table.
9. Publish the CoE BYODL Environments dataflow and wait for the refresh to finish.
10. Edit the CoE BYODL Apps, CoE BYODL Model Driven Apps, and CoE BYODL Flows dataflows. Complete the same steps to update the DatalakeURL and EnvironmentAPI parameters and configure the connections to the data sources used by this dataflow.
11. Confirm that the CoE BYODL Apps and CoE BYODL Model Driven Apps dataflows are configured to load data to the existing admin_App table. The CoE BYODL Flows dataflow should be configured to load data to the existing admin_Flow table.
12. Publish the CoE BYODL Apps, CoE BYODL Model Driven Apps, and CoE BYODL Flows dataflows and wait for the refresh to finish.
13. Edit the CoE BYODL Apps Connection, CoE BYODL Apps Last Launched Date, CoE BYODL Flows Connection, and CoE BYODL Flows Last Run Date dataflows. Complete the same steps to update the DatalakeURL and EnvironmentAPI parameters and configure the connections to the data sources used by this dataflow.
14. Confirm the CoE BYODL Apps Connection and CoE BYODL Apps Last Launched Date dataflows are configured to load data to the existing admin_App table. The CoE BYODL Flows Connection and CoE BYODL Flows Last Run Date dataflows should be configured to load data to the existing admin_Flow table.
15. Publish the CoE BYODL Apps Connection, CoE BYODL Apps Last Launched Date, CoE BYODL Flows Connection, and CoE BYODL Flows Last Run Date dataflows and wait for the refresh to finish.

Troubleshooting

The specified path doesn't exist

This dataSource error means not all required folders and files are available yet in the storage account, since you recently configured the Data Export. After the initial setup, seeing updated data can take up to five days for folders to populate.

A DataFormat.Error after updating the DatalakeURL and EnvironmentAPI parameters

This error might mean you entered the incorrect URLs. Verify that the DatalakeURL parameter points to your Azure Storage account URL. The URL should contain dfs.core and end with /powerplatform. Verify that the EnvironmentAPI points to your Environment Web API. The URL should contain api.crm and end with /api/data/v9.2.

The publish or refresh failed

Select the error to review the status alert in the Last refresh column.

The refresh might fail if you didn't configure connections to all data sources used by the dataflow. Edit the dataflow again and verify you configured the connections to all data sources. Select all the queries individually to check for warnings.

The publish button is disabled

If you configured connections in the dataflow, but the Publish button remains disabled (with a warning message), some configured connections might be missing. Select Back and review all queries for connection warnings.

Configure scheduled refresh

1. Navigate to make.powerapps.com.
2. Select the environment installed with the CoE Starter Kit.
3. Select Dataflows.
4. Select Edit refresh settings for the CoE BYODL Makers dataflow.
5. Select Refresh automatically and configure a daily refresh. Check when files write to your storage account by the Data Export feature and set the daily refresh of the dataflow after that time. The dataflow now runs after data is exported to your storage account.

Environment variables

This section includes the full list of environment variables that affect the Data Export methodology to inventory the tenant. These values are all filled for you by the Setup Wizard.

Name	Description	Default value
App Connections Dataflow ID	Dataflow ID of the CoE BYODL App Connections dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
App Dataflow ID	Dataflow ID of the CoE BYODL Apps dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
App Usage Dataflow ID	Dataflow ID of the CoE BYODL App USage dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Current Environment	Current Dataflow Environment ID used by cloud flows to refresh dataflows. Only used when mechanism for inventory is Data Export.	Not applicable
Environment Dataflow ID	Dataflow ID of the CoE BYODL Environments dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Flow Connections Dataflow ID	Dataflow ID of the CoE BYODL Flow Connections dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Flow Usage Dataflow ID	Dataflow ID of the CoE BYODL Flow Usage dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Flow Dataflow ID	Dataflow ID of the CoE BYODL Flows dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Maker Dataflow ID	Dataflow ID of the CoE BYODL Makers dataflow. Only used when mechanism for inventory is Data Export.	Not applicable
Model App Dataflow ID	Dataflow ID of the CoE BYODL Model Driven Apps dataflow. Only used when mechanism for inventory is Data Export.	Not applicable

I found a bug with the CoE Starter Kit; where should I go?

To file a bug against the solution, go to aka.ms/coe-starter-kit-issues.