Microsoft Dynamics 365
change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.Grade D · dataset: API (the vendor’s response payloads) · type d365
What it is
Microsoft Dynamics 365 Finance & Operations read over OData data entities. In the test estate it is accounts payable: carrier vendors and their invoice headers.
Grade
D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.
See the grade table for all 32 types.
Settings and credentials
From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.
| Names | |
|---|---|
| Type | d365 |
| Other spellings that resolve | dynamics365, dynamics |
| Settings | base_url, tenant_id, client_id |
| Credentials | client_secret |
The test connection
Quillmere finance (Dynamics 365)
| Setting | Test value |
|---|---|
base_url | https://quillmere.operations.dynamics.invalid |
tenant_id | 00000000-0000-4000-8000-000000000001 |
client_id | 00000000-0000-4000-8000-000000000002 |
Credentials: client_secret. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.
Stand up the test system
The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.
- Download
d365.zipand unzip it. It holds the vendor’s response payloads andexpected.json. - There is no local edition: Dynamics 365 needs a Microsoft 365 tenant.
- Open the payloads next to
expected.json: every field the expected model names is in the payload, with the join keys described below.
What FACE finds
FACE reads no catalogue for this type. The dataset is Finance & Operations OData data-entity responses, and the expected model is their record shape.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
VendorsV2 | data_entity | carriers | dataAreaId, VendorAccountNumber | 4 | 4 |
VendorInvoiceHeaders | data_entity | finance | dataAreaId, HeaderReference | 24 | 9 |
expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.
How it joins the Quillmere universe
This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.
| Universe entity | Fields here | Also in |
|---|---|---|
| carrier | VendorInvoiceHeaders.InvoiceAccount, VendorsV2.VendorAccountNumber | document, files, guidewire, mysql, objectstore, postgres, redshift, sharepoint, tms, yms |
| invoice | VendorInvoiceHeaders.InvoiceNumber | files, mysql, objectstore, redshift |
| shipment | VendorInvoiceHeaders.QFLShipmentId | bigquery, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms |
Evidence it holds for the planted anomalies:
- ANOM-1, An overcharged freight invoice.
d365/data_VendorInvoiceHeaders.jsonind365.zip, look for"InvoiceAmount": 494.01(approved for payment at the billed amount).
See all connectors at once for the walkthrough across every source.
Download
d365.zip: 3 files,expected.jsonincluded.
This is one of 25 zips: the 7 streaming types ship as replay recordings instead.
What is in the zip
d365/data_VendorsV2.jsond365/data_VendorInvoiceHeaders.jsond365/expected.json
The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.