> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365-finance-and-operations.md). # Dynamics 365 Finance & Operations The **Dynamics 365 Finance & Operations** connector enables integrations with [Microsoft Dynamics 365 Finance & Operations](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/) (F\&O), also known as Finance and Supply Chain Management. It reads and writes the app's public **OData data entities**, such as `CustomersV3`, `VendorsV2`, `SalesOrderHeadersV2`, and `ReleasedProductsV2`. Supported operations include CRUD, query options, bound and unbound actions and functions, cross-company access, and `$batch`. It's a specialization of the generic OData integration, using the `/data` service root, composite `dataAreaId` keys, and Azure AD (Azure Key) authentication. Entities are discovered automatically from the environment's `$metadata`, and cross-company access is supported. {% hint style="info" %} #### **Which Dynamics connector should I use?** Use **Dynamics 365 Finance & Operations** for Finance and Supply Chain (`*.operations.dynamics.com`, `/data` entities). Use [**Dynamics 365**](/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365.md) for Customer Engagement, Dataverse, and CRM (`*.crm.dynamics.com`, `/api/data/v9.x`). Use the generic [**OData**](/documentation/connectors-and-triggers/connectors/web-protocols/odata.md) connector for any other OData service. {% endhint %} ## **Set up authentication (Azure AD)** The connector authenticates as an Azure AD **service principal** (OAuth 2.0 client credentials). You set this up once. Below are the steps relevant to Digibee. For the exact portal clicks, follow the linked Microsoft docs, since their UI changes over time. 1. **Register an app** in Microsoft Entra ID. In the Entra admin center, go to **App registrations**, then **New registration**. Copy the **Application (client) ID** and the **Directory (tenant) ID**. See [Register an application](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) for the full procedure. 2. **Create a client secret.** Go to **Certificates & secrets**, then **Client secrets**, then **New client secret**. Copy the secret **value** right away, it's shown only once. See [Add and manage app credentials](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials) for the full procedure. 3. **Grant the app access inside Finance & Operations.** In the F\&O app, go to **System administration**, then **Setup**, then **Microsoft Entra ID applications**. Add a row with the app's **Client ID**, a name, and a **User ID** mapped to a user whose **security role** grants access to the entities you'll use. {% hint style="warning" %} **Step 3 is required.** Skip it, and requests will still **authenticate** (a valid token is issued), but they'll get **rejected** with `401`/`403`, because the service principal isn't authorized in F\&O. {% endhint %} 4. **Create the Digibee Azure Key account** using the values from steps 1 and 2: | Azure Key account field | Value | | ----------------------- | -------------------------------- | | Client ID | Application (client) ID (step 1) | | Client Secret | The secret **value** (step 2) | | Tenant ID | Directory (tenant) ID (step 1) | The connector requests the token for scope `https://{your-env}.operations.dynamics.com/.default`. Only override it with **OAuth Scope** if your resource differs. See [Accounts](/documentation/developer-guide/development-cycle/build-overview/accounts.md). {% hint style="info" %} Client secrets expire. Microsoft caps them at 24 months and recommends less. Rotate the secret and update the Azure Key account before it expires, or discovery and requests will start failing with auth errors. {% endhint %} You'll also need the **environment URL**, for example `https://myenv.operations.dynamics.com`. ## **Concepts** The terms below appear throughout the connector's parameters, so it helps to understand them before configuring a request. Each concept maps to a specific field you'll fill in later.
TermMeaning
Data entityThe OData collection you're working with, for example CustomersV3. Path: /data/CustomersV3.
Composite keyF&O keys are usually composite and include dataAreaId (the legal entity, or company), for example dataAreaId='usmf',CustomerAccount='US-001'.
Cross-companyBy default, a query returns only the user's default company. Enable Cross-company to span all legal entities (cross-company=true).
$metadataF&O exposes entity and field metadata at /data/$metadata. The connector uses it to power the guided Entity Set picker and field editor.
## **Parameters** The table below lists all configuration parameters for the connector. Parameters that support [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with ✅ in the **Supports DB** column. {% tabs %} {% tab title="General" %}
ParameterDescriptionTypeSupports DBDefault
AliasA name for this connector's output, so you can reference it later in the flow with Double Braces.String✅dynamics-finops-01
Fail On Client Error (4xx)Interrupt the pipeline on a 4xx response.Boolean❌false
Fail On Server Error (5xx)Interrupt the pipeline on a 5xx response.Boolean❌false
{% endtab %} {% tab title="Authentication" %}
ParameterDescriptionTypeSupports DBDefaultVisible when
Environment URLFinance & Operations environment root URL.String✅https://myenv.operations.dynamics.com—
Use Dynamic AccountIf enabled, the connector resolves the account at runtime. If disabled, it uses the account configured statically below.Boolean❌falseUse Dynamic Account is enabled
ScopedIf enabled, isolates the stored account from other sub-processes. Not available for accounts referenced in headers or in the request body. To learn more, read the Dynamic Accounts documentation.Boolean❌falseUse Dynamic Account is enabled
Account NameName of the account defined in the Store Account connector.String✅N/AUse Dynamic Account is disabled
AccountAccount containing the Azure AD credentials (client ID, secret, and tenant). Supported type: Azure Key. Learn more about Accounts.Account—N/A
{% hint style="info" %} Authentication uses the OAuth 2.0 client-credentials flow with Azure AD (Microsoft Entra ID) and injects the resulting token as a `Bearer` header. The token is cached per combination of client, tenant, and scope. OData v4 is used and fixed for Finance & Operations. {% endhint %} {% endtab %} {% tab title="Dynamics API" %} ### **Operation parameter**
ParameterDescriptionTypeSupports DBDefault
OperationThe action to perform. It shapes the request. See the supported operations below.Select❌Query
#### **Supported operations** The **Operation** parameter maps to an OData request under the `/data` service root:
OperationHTTPPathBodyNotes
BatchPOST/data/$batchmultipart/JSONBatches multiple operations in one request.
CreatePOST/data/{EntitySet}JSONCreates a record.
Custom QueryGET/data/{EntitySet}?{$query}—Same as Query. Use it when combining raw and structured query parameters.
DeleteDELETE/data/{EntitySet}({key})—Deletes a record.
Get by IDGET/data/{EntitySet}({key})—Reads a single record by key.
Invoke ActionPOST/data/{EntitySet}({key})/{Action} or /data/{Action}JSONInvokes a bound action (with key and entity set) or an unbound action.
Invoke FunctionGET/data/{EntitySet}({key})/{Function} or /data/{Function}—Invokes a bound or unbound function.
QueryGET/data/{EntitySet}?{$query}—Reads the collection with query options.
UpdatePATCH/PUT/data/{EntitySet}({key})JSONUpdates a record, partially (PATCH) or fully (PUT).
### **Common parameters** These parameters appear regardless of the operation selected.
ParameterDescriptionTypeSupports DBDefault
Cross-companyReturns rows across all legal entities, instead of only the default company (cross-company=true).Boolean❌false
Output FormatControls the shape of the response returned to the pipeline. Values Only unwraps and returns only the value array. Full Response returns the entire response, including @odata.* fields. Single Entity returns the first or only entity.Select❌Values Only
HeadersAdditional request headers, as key/value pairs.Key/Value✅N/A
### **Operation-specific parameters** The remaining parameters only appear for certain operations, grouped below by purpose. **Entity Key** — used by **Delete**, **Get by ID**, **Invoke Action**, **Invoke Function**, and **Update**.
ParameterDescriptionTypeSupports DBDefault
Entity KeySingle or composite key. F&O keys are usually composite, for example dataAreaId='usmf',CustomerAccount='US-001'.String✅N/A
**Action / Function Name** — used by **Invoke Action** and **Invoke Function**.
ParameterDescriptionTypeSupports DBDefault
Action / Function NameOData action or function name. Bound when an Entity Set is set, unbound otherwise.String✅N/A
**Body** — used by **Batch**, **Create**, **Invoke Action**, and **Update**.
ParameterDescriptionTypeSupports DBDefault
BodyJSON payload for Create and Update, action parameters for Invoke Action, or the $batch payload.JSON✅{}
**Interactive Mode** — used by **Create** and **Update**.
ParameterDescriptionTypeSupports DBDefault
Interactive ModeIf enabled, the connector displays the payload fields for you to edit. Otherwise, provide a raw JSON body.Boolean❌false
**Query parameters** — used by **Custom Query** and **Query**.
ParameterDescriptionTypeSupports DBDefault
Filter ($filter)OData filter expression, for example CustomerGroupId eq '10'.String✅N/A
Select ($select)Comma-separated list of fields to include in the response.String✅N/A
Order By ($orderby)Sorts the results by one or more properties, in ascending or descending order, for example CustomerAccount asc.String✅N/A
Expand ($expand)Related entities to include inline.String✅N/A
Top ($top)Maximum number of records to return.Number✅N/A
Skip ($skip)Records to skip, for pagination.Number✅N/A
Include Count ($count)Include the total count in the response.Boolean❌false
{% endtab %} {% tab title="Advanced Settings" %}
ParameterDescriptionTypeSupports DBDefaultVisible when
Request Timeout (seconds)Maximum time for the HTTP request.Integer❌30—
Custom Query StringRaw extra query parameters appended verbatim.String✅N/A—
Update MethodPATCH for a partial update, or PUT for a full replacement.Select❌PATCHOperation is Update
{% endtab %} {% tab title="Documentation" %}
ParameterDescriptionData typeSupports DBDefault value
DocumentationOptional field to describe the connector configuration and any relevant business rules.String❌N/A
{% endtab %} {% endtabs %} ## **Examples** ### **Query customers in one company** ``` Environment URL = https://myenv.operations.dynamics.com Entity Set = CustomersV3 Operation = Query Select = CustomerAccount,OrganizationName Filter = CustomerGroupId eq '10' Top = 2 ``` **Resulting request:** {% code overflow="wrap" %} ```html GET /data/CustomersV3?$select=CustomerAccount,OrganizationName&$filter=CustomerGroupId eq '10'&$top=2 ``` {% endcode %} **Output** (when the Output Format is set to `Values Only`) : ```json [ { "CustomerAccount": "US-001", "OrganizationName": "Contoso Retail" }, { "CustomerAccount": "US-004", "OrganizationName": "Fabrikam" } ] ``` ### **Get one record by composite key** ``` Entity Set = CustomersV3 Operation = Get by ID Entity Key = dataAreaId='usmf',CustomerAccount='US-001' ``` **Resulting request:** ```html GET /data/CustomersV3(dataAreaId='usmf',CustomerAccount='US-001') ``` ### **Query across all companies** ``` Entity Set = SalesOrderHeadersV2 Operation = Query Cross-company = true ``` **Resulting request:** ```html GET /data/SalesOrderHeadersV2?cross-company=true ``` ## **Known limitations** * OData v4 only. Finance & Operations doesn't expose v2. * No FetchXML. That's Dataverse and CRM-only. Use the [**Dynamics 365**](/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365.md) connector for that. * No automatic pagination. Follow `@odata.nextLink` yourself, or control paging manually with `$top` and `$skip`. * Guided entity and field discovery requires a reachable environment and a valid Azure Key account. If discovery can't reach the environment, you can still provide the Entity Set through a Double Braces expression. * Composite keys, `@odata.bind` lookups for navigation properties, and enum and option values are the most error-prone areas. Validate against the entity's `$metadata`. ## **Common errors**
StatusCause
400Malformed composite key syntax or $filter expression.
401 / 403The app isn't registered as an F&O Application User, is missing the required security role, or the token scope is wrong.
404Wrong entity set name.
Enable **Fail On Client Error (4xx)** or **Fail On Server Error (5xx)** to have the connector stop the pipeline when these errors occur. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365-finance-and-operations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.