Microsoft Dataverse¶
Microsoft Dataverse is secure, cloud-based table storage for business applications, such as those belonging to the Microsoft Power Platform (Power BI, Power Apps, Power Automate, Power Virtual Agents, and Power Pages), Microsoft 365, Microsoft Azure, Dynamics 365, and other standalone applications.
This topic describes the steps that are required to send table rows that match a table schema to Microsoft Dataverse from Amperity:
How this destination works¶
Use the Microsoft Dataverse destination to send rows of data from Amperity, and then add them to tables in Microsoft Dataverse. The connector will validate each row of data that is sent from Amperity against the table schema in Microsoft Dataverse. Only rows that validate against the table schema will be added to the table.
A Microsoft Dataverse destination works like this:
Use a query to build a table with rows of data that match the schema of a table in Microsoft Dataverse. The column names, data types, and column order must match the schema that is defined in Microsoft Dataverse.
Configure the Microsoft Dataverse destination in Amperity.
Validated table rows are sent to Microsoft Dataverse.
Get details¶
Amperity can be configured to send table rows that match a table schema to Microsoft Dataverse.
Microsoft Azure must be configured for your Power Apps application, after which your Power Apps application must be added to the Microsoft Power Platform.
You will need to provide your Azure tenant ID, Azure client ID, and your Azure client secret.
The environment region, environment name, and logical table name for your Power Apps application. For example: “crm” (region), “acme” (name), and “abc123_acme” (table name).
Configure your Microsoft application¶
To send data to Microsoft Dataverse, you need to configure an application in Microsoft Azure to create the application and directory IDs and a client secret, after which you must add your application to the Microsoft Power Platform.
To configure your application in Microsoft Azure
Log in to your Microsoft Azure account.
Open Azure Active Directory, and then App Registrations.
Click New Registration, and then enter the name for your application. Leave all other settings as the default, and then click Register.
The application overview page contains the following IDs:
Application (client) ID
Directory (tenant) ID
From the left-side navigation, click Authentication, then Add a platform, and then Web.
On the next page, in the Redirect URI field, enter:
https://app.amperity.com.Under Implicit grant and hybrid flows, enable the Access tokens (used for implicit flows) option, and then click Configure.
From the left-side navigation, click Certificates & Secrets, select the Client secrets tab, and then click New client secret.
From the left-side navigation, click API Permissions, select Add a permission, select Dynamics CRM, select user_impersonation, and then click Add permissions.
To add your application to the Microsoft Power Platform
Open the Microsoft Power Platform console , click Environments, and then click on your environment.
Click Settings, then Users and permissions, and then Application users.
Click New app user, and then select the application you just created, your business unit, and then under Security roles click the Edit button.
Select the following settings:
Service Reader
Service Writer
and then click Save.
Click Create.
Add destination¶
Configure Amperity to send table rows that match a table schema to Microsoft Dataverse.
To add a destination
From the Destinations tab, click Add Destination. This opens the Add Destination dialog box.
Enter the name of the destination and a description. For example, “Microsoft Dataverse” and “Send table rows that match a table schema in Microsoft Dataverse”.
From the Plugin drop-down, select “Microsoft Dataverse”.
The “microsoft-dataverse” credential type is selected automatically.
From the Credential drop-down, select a credential that has already been configured for this destination or click Create a new credential, which opens the Create New Credential dialog box. For new credentials, enter the Azure tenant ID, Azure client ID, and your Azure client secret. Click Save.
Select Allow business users to use this destination.
This allows users who have been assigned to the Amp360 User and/or AmpIQ User policies to use this destination with orchestrations and/or campaigns.
Select Allow business users with limited PII access to send data.
This allows users who have been assigned to the Restrict PII Access policy option to use this destination with orchestrations and/or campaigns.
Click Save.
Add data template¶
A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.
You can configure Amperity to send query results to Microsoft Dataverse. These results are sent using an orchestration and will include all columns that were specified in the query.
To add a data template for orchestrations
From the Destinations tab, open the menu for a destination that is configured for Microsoft Dataverse, and then select Add data template.
This opens the Add Data Template dialog box.
Enter the name of the data template and a description. For example: “Microsoft Dataverse customer profiles” and “Send data to Microsoft Dataverse.”
Enable the Allow customers to use this data template option. This allows users to build queries, and then configure orchestrations that send results from Amperity to a configured destination.
Optional. Enable the Allow orchestrations from customers with limited PII access option. This allows users who have been assigned the Restrict PII Access policy option to send results from Amperity.
Verify all template settings and make any required updates.
Power Apps Environment Region The region in which your data center is located. For example: “crm”.
Power Apps Environment Name The unique name for your Power Apps environment. For example: “acme”.
Dataverse Table Logical Name The table name in Microsoft Dataverse. This is the table to which the connector will write data. For example: “abc123_customers”.
Select Truncate? to truncate the table before loading data.
Click Save.