Microsoft Dynamics 365 Finance and Operations modules and their fields

IMPORTANT
The data entities available through the Dynamics 365 F&O API can vary by instance. If you are not sure what entities are available through the API, it’s useful to look through the entities in your instance using the “data” endpoint. The “data” endpoint in Dynamics 365 Finance and Operations is the root URL for accessing OData services. This endpoint allows you to interact with various data entities exposed by the system using standard OData protocols.
You can retrieve these entities using the custom API call module.

Create entity item

This action module creates a new entity item in Microsoft Dynamics 365 Finance and Operations.

ConnectionFor instructions about connecting Microsoft Dynamics 365 Finance and Operations to Workfront Fusion, see Create a connection in this article.
EntityEnter or map the Dynamics Finance and Operations entity type that you want to create.
BodyEnter or map a JSON body that contains the data that you want to include in the new entity item.

Delete entity item

This action module deletes an entity item from Dynamics Finance and Operations. The item is identified by its Primary key fields.

ConnectionFor instructions about connecting Microsoft Dynamics 365 Finance and Operations to Workfront Fusion, see Create a connection in this article.
EntityEnter or map the Dynamics Finance and Operations entity type that you want to delete.
Primary key fieldsThe Primary key fields identify the item. For each primary key field that you want to provide, click Add item and enter or map the unique key and value that identify that item.

Make a custom API call

This action module makes a custom call to the Dynamics Finance and Operations API.

ConnectionFor instructions about connecting Microsoft Dynamics 365 Finance and Operations to Workfront Fusion, see Create a connection in this article.
URLEnter a path relative to your Dynamics Finance and Operations URL.
MethodSelect the HTTP request method you need to configure the API call. For more information, see HTTP request methods.
Headers

Add the headers of the request in the form of a standard JSON object. This determines the content type of the request.

For example, {"Content-type":"application/json"}

Note: If you're getting errors and it's difficult to determine their origin, consider modifying headers based on the Workfront documentation. If your Custom API Call returns a 422 HTTP Request Error, try using a "Content-Type":"text/plain" header.

Query string

Add the query for the API call in the form of a standard JSON object.

For example: {"name":"something-urgent"}

Tip: We recommend that you send information through the JSON body rather than as query parameters.

Body

Add the body content for the API call in the form of a standard JSON object.

Note:

When using conditional statements such as if in your JSON, put the quotation marks outside of the conditional statement.