Skip to content

Microsoft Dynamics 365

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: 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
Typed365
Other spellings that resolvedynamics365, dynamics
Settingsbase_url, tenant_id, client_id
Credentialsclient_secret

The test connection

Quillmere finance (Dynamics 365)

SettingTest value
base_urlhttps://quillmere.operations.dynamics.invalid
tenant_id00000000-0000-4000-8000-000000000001
client_id00000000-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.

  1. Download d365.zip and unzip it. It holds the vendor’s response payloads and expected.json.
  2. There is no local edition: Dynamics 365 needs a Microsoft 365 tenant.
  3. 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.

DatasetKindDomainPrimary keyRowsFields
VendorsV2data_entitycarriersdataAreaId, VendorAccountNumber44
VendorInvoiceHeadersdata_entityfinancedataAreaId, HeaderReference249

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 entityFields hereAlso in
carrierVendorInvoiceHeaders.InvoiceAccount, VendorsV2.VendorAccountNumberdocument, files, guidewire, mysql, objectstore, postgres, redshift, sharepoint, tms, yms
invoiceVendorInvoiceHeaders.InvoiceNumberfiles, mysql, objectstore, redshift
shipmentVendorInvoiceHeaders.QFLShipmentIdbigquery, 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.json in d365.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.json included.

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • d365/data_VendorsV2.json
  • d365/data_VendorInvoiceHeaders.json
  • d365/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.