Connect DataBusiness Apps
Microsoft Dynamics 365
Microsoft Dynamics 365 is in Preview in the connection wizard: it is built on Microsoft Dynamics 365’s documented API and has not yet been proven against a live account, so check the imported tables before relying on them. Register an app in Microsoft Entra ID with a client secret, then add it to the environment as an application user with a security role that can read these tables (Power Platform admin center → Environments → Settings → Users + permissions → Application users). Commercial cloud only.
-
In DataSquares, open Data Sources and choose Connect Source. The Connect a data source page opens.
-
Pick Microsoft Dynamics 365 on that page (search or browse by category).
-
Fill in the connection details below, then test the connection and save.
Connection details
Section titled “Connection details”| Field | What to enter |
|---|---|
| Environment | The first part of your environment URL: contoso in contoso.crm4.dynamics.com. e.g. contoso |
| Region | The part after it: crm (North America), crm4 (Europe), crm11 (UK), crm5 (Asia Pacific) … Default crm. |
| Directory (tenant) ID | Microsoft Entra ID → your app registration → Overview. |
| Application (client) ID | — |
| Client secret | The app registration → Certificates & secrets → a client secret (its value). Stored encrypted and never shown again. |
Test Connection reads one page of records with these values; nothing is saved until you import.
Tables
Section titled “Tables”Pick the tables to import — each one becomes a table in the source:
| Table | What it holds |
|---|---|
accounts |
Accounts |
contacts |
Contacts |
leads |
Leads — Only in environments created with Dynamics 365 apps enabled. |
opportunities |
Opportunities — Only in environments created with Dynamics 365 apps enabled. |
incidents |
Cases — Only in environments created with Dynamics 365 apps enabled. (not selected by default) |
systemusers |
Users |
Choice, lookup and money columns also arrive as <column>_label — the text
Microsoft Dynamics 365 shows for them (a lookup’s id stays in its _<name>_value column).
Every table is read through all of its pages, nested fields become parent.child
columns, and the whole set is imported at once: the import’s row and size limits
count the picked tables together, and if they pass one, nothing is imported and
the message says which table and which limit. Refresh the source on a schedule,
or by hand, to re-read every table; a table that comes back empty is refused
rather than emptied unless you allow it. Nothing is ever written to Microsoft Dynamics 365.
The requests follow Microsoft Dynamics 365’s API reference.
Related
Section titled “Related”- Connector catalog — everything DataSquares connects to.
- Quickstart — from connection to shared dashboard.