---
title: Create an Incident Work Order in Microsoft Dynamics
description: Configure a TrueContext form to detect a regulatory incident during a field inspection and automatically create a follow-up incident work order in Microsoft Dynamics 365 Field Service using an on-demand data source Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data., Conditional Logic, and a Webhook question.
meta_tier: Advanced-Enterprise
meta_component: Webhooks
source_file: DynamicsRecipe.htm
url: https://docs.truecontext.com/1374411/Content/DynamicsRecipe.htm
last_updated: '2026-06-02'
word_count: 2426
---

# Create an Incident Work Order in Microsoft Dynamics

This recipe shows you how to use an On-Demand HTTP GET Data Source to look up an existing work order. You then combine it with a Webhook question to post a new related incident work order back to Microsoft Dynamics.

Available on the Elite tier:

—Digital

—Intelligent

Elite

[?](https://truecontext.com/pricing/)

---

## Use case

A technician is working on a scheduled work order and records gas readings and visual checks for hydrocarbon releases. If the readings exceed a regulatory threshold or there is a visible release, the technician must declare a reportable incident immediately. This triggers a follow-up work order in Microsoft Dynamics for the incident investigation.

This recipe shows how to configure the form, Data Source, and Webhook. The technician can then select the original work order, capture incident details, and create a linked incident work order in Microsoft Dynamics from a single TrueContext form.

## Prerequisites

- A Microsoft Dynamics 365 Field Service environment with work orders, service accounts, customer assets, and incident types configured.
- A Microsoft Dynamics API user or app registration with permission to read and create work orders or incidents by using the Web API.
- A TrueContext HTTP Connection for Microsoft Dynamics, including authentication and the base Web API URL.

## High-level process

Setting up this recipe requires completing the following steps:

| Step | Action |
| --- | --- |
| 1 | Create a Dataverse Connection |
| 2 | Configure the Microsoft Dynamics HTTP GET Data Source |
| 3 | Create the Microsoft Dynamics POST Webhook |
| 4 | Configure the Regulatory Incident Declaration form |
| 5 | Configure the Microsoft Dynamics Webhook question |
| 6 | Configure Conditional Logic |
| 7 | Test this recipe |

### 1. Create a Dataverse Connection

Create a Dataverse Connection that TrueContext can use to authenticate to Microsoft Dynamics and send Data Source and Webhook requests.

[Set Up an HTTP Connection to Microsoft Dataverse](HTTPDynamicsConnection.md).

### 2. Configure the Microsoft Dynamics HTTP GET Data Source

The On-DemandData Source lets the technician select an existing Microsoft Dynamics work order and pulls related values into hidden questions on the form.

| Step | Action |
| --- | --- |
| 1 | Go to Forms & Integrations Integration refers to secure communication and data sharing between TrueContext and a third-party system, such as Salesforce or ServiceMax. Connections, Data Sources, Data Destinations, and App-to-App calls and callbacks can be used as part of an integration solution. > Data Sources Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data. > Create Data Source > HTTP GET Data Source . |
| 2 | On the Name tab, enter a name, then select Enable on-demand data retrieval on your connected devices . |
| 3 | On the Data Retrieval and Format tab, select JSON for Input Configuration > Data Format . |
| 4 | On the Connection tab, select the Dataverse Connection you created. |
| 5 | Set the URL Path to /api/data/v{{apiVersion}}/msdyn_workorders . Add an apiVersion parameter for your Microsoft Dynamics API version. In this recipe, we use API version = 9.2 . |
| 6 | Add the following Query-String Argument to return the Dynamics work order columns you want to use in the form: Argument Key Argument Value $select msdyn_autonumbering,msdyn_workorderid,msdyn_name,createdon,msdyn_systemstatus,msdyn_workordersummary,_msdyn_serviceaccount_value,_msdyn_workordertype_value,_msdyn_primaryincidenttype_value,_msdyn_customerasset_value,_msdyn_functionallocation_value |
| 7 | Add the following HTTP Headers: Header Key Header Value Accept application/json Prefer odata.include-annotations="OData.Community.Display.V1.FormattedValue" Dataverse lookup columns return a GUID, so this header is necessary to also return a user-friendly value. |

Learn more by reading [Set Up On-Demand Data Sources](../Features/DataSources/OnDemandDataSources/SetUpODDS.md).

### 3. Create the Microsoft Dynamics POST Webhook

Create a FormSpace FormSpaces are where forms are stored and organized in the TrueContext Web Portal. A TrueContext Team may have multiple FormSpaces, depending on their needs. Admins can set FormSpace permissions to control which users have access to the forms in that FormSpace.-level POST webhook in the web portal. This webhook defines the API call that creates a new incident work order in the Microsoft Dynamics `msdyn_workorders` table.

| Step | Action |
| --- | --- |
| 1 | Go to Forms & Integrations > Webhooks > CREATE WEBHOOK > HTTP Webhook . |
| 2 | On the Name tab, enter a name for the webhook, for example Dynamics POST . |
| 3 | On the Connection tab, select the Dataverse Connection you created. |
| 4 | In Request Configuration , set HTTP Method to POST and set URL Path to /api/data/v9.2/msdyn_workorders . Leave Query Parameters empty. |
| 5 | Add the following HTTP headers: Name Value Content-Type application/json Prefer return=representation The Prefer: return=representation header tells Dynamics to return the created work order record in the response. This lets the Webhook question display and route the new work order number. |
| 6 | Set Body Format to Raw and enter the following in Raw Body Template : { "msdyn_serviceaccount@odata.bind": "/accounts({{service_account_guid}})", "msdyn_customerasset@odata.bind": "/msdyn_customerassets({{customer_asset_guid}})", "msdyn_primaryincidenttype@odata.bind": "/msdyn_incidenttypes({{incident_type_guid}})", "msdyn_systemstatus": 690970000 } The double-brace syntax ( {{parameter_name}} ) marks values that the mobile device substitutes at run time from form questions. The value 690970000 is the Microsoft Dynamics option set code for an Unscheduled work order status. |
| 7 | In Test Request , confirm that the Parameters section shows the three parameters derived from the body template: service_account_guid , customer_asset_guid , and incident_type_guid . Enter sample GUID values for each parameter and select Test Webhook to confirm the connection and request are configured correctly. |
| 8 | Select Create to save the webhook. The Dynamics POST webhook is now available to add to forms in your FormSpace. |

Learn more by reading [Set Up a Webhook](2SetUpWebhooks.md).

### 4. Configure the Regulatory Incident Declaration form

The form uses one page for selecting and pre-populating work order info, and another for the incident checklist and follow-up incident work order details.

| Step | Action |
| --- | --- |
| 1 | Create a page named Work Order and section named Information . |
| 2 | Add a question, API version , a hidden Text Field question with a default value of 9.2 , used as a parameter for the Microsoft Dynamics HTTP GET Data Source. |
| 3 | Add a Select Work Order dropdown question. |
| 4 | In Select Data Source , choose the On-Demand HTTP GET Data Source you created in the previous section. |
| 5 | In the Data Source configuration section, set the Column value displayed on device to msdyn_autonumbering. |
| 6 | Add Text Field questions to store the following values returned by the Dynamics Data Source: Work Order ID and Work Order Number Work Order Type ID and Work Order Type Service Account ID (Label: service_account_guid)and Service Account Name Customer Asset ID (Label: customer_asset_guid) and Customer Asset Name Add Hidden on Device and Read only Restrictions to ID questions. If question labels are specified, make sure to use them exactly as written, so they match the response body. |
| 7 | Return to the Select Data Source question form step 3. In the Push Data to Other Questions section, select the Work Order Text Field questions we added in step 6. |
| 8 | Create a page named Checklist and add the following questions: Gas Reading (%LEL) : A Text Field (Decimal) where the technician enters the measured gas concentration. Visible Hydrocarbon Release : A Button Group with Yes and No options. Regulatory Threshold : A Hidden on Device Text Field (Decimal) with a default threshold value, for example 10 , used in Conditional Logic. Confirm declaration of reportable incident : A Button Group with Yes and No options. This question appears when Conditional Logic detects that the gas reading or release indicator meets the incident criteria. |
| 9 | Create a manual Incident Type GUID Mapper Data source, with two columns, Incident Type, and Incident Type GUID, fill this Data Source with your Dynamic Incident Type information. An alternative is to execute a separate GET request to Dynamics, to return the GUID for the Incident Type selected in the form. |
| 10 | Add a section named Incident Report to the Checklist page and add the following questions: Parent Work Order ID : A Read Only Text Field that stores the work order ID from the selected work order. Incident Service Account Name : A Read Only Text Field that shows the service account name. Incident Customer Asset : A Read Only Text Field that shows the customer asset name. Incident Type : A Dropdown connected to the manual Incident Type GUID Mapper Data Source from step 9. In the question configuration, choose to push the Incident Type GUID to the next question. Incident Type GUID (Label: incident_type_guid): A Hidden on Device Text Field populated automatically with the value of the Incident Type GUID selected in the previous question. Create Incident Work Order in Dynamics : A Webhook question that creates the follow-up incident work order in Microsoft Dynamics. Incident Work Order Number : In the Webhook question, this field is configured to display the parsed response for msdyn_name . |

### 5. Configure the Microsoft Dynamics Webhook question

The Webhook question referenced in the previous steps sends a POST request to Microsoft Dynamics, using the incident context from the form.

<table style="width: 100%; border-collapse: collapse;">
<col style="width: 5%;"/>
<col style="width: 25%;"/>
<col style="width: 70%;"/>
<thead>
<tr>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Step</th>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Section</th>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Action</th>
</tr>
</thead>
<tbody>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">1</td>
<td rowspan="4" style="padding: 8px; border: 1px solid #ccc; vertical-align: top;"><span class="uiElement">Webhook Configuration</span>
</td>
<td style="padding: 8px; border: 1px solid #ccc;">Select the Dynamics POST Webhook you previously created.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">2</td>
<td style="padding: 8px; border: 1px solid #ccc;">For Response usage, select both boxes: the first displays the answer inline in the Webhook question, and the second identifies the Webhook as using the response to route to other questions on the form.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">3</td>
<td style="padding: 8px; border: 1px solid #ccc;">Set the Webhook trigger to Manual. The technician selects <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Run Action</span> on the Webhook question to create the incident work order.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">4</td>
<td style="padding: 8px; border: 1px solid #ccc;">Add parameters that map to the corresponding form questions, for example:

                        <ul><li><code>service_account_guid</code> from the <span class="uiElement">Service Account ID</span> question.</li><li><code>customer_asset_guid</code> from the <span class="uiElement">Customer Asset ID</span> question.</li><li><code>incident_type_guid</code> from the <span class="uiElement">Incident Type GUID</span> question.</li></ul></td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">5</td>
<td rowspan="2" style="padding: 8px; border: 1px solid #ccc; vertical-align: top;"><span class="uiElement">Answer Definition</span>
</td>
<td style="padding: 8px; border: 1px solid #ccc;">Select  <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">JSON</span> as the <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Response Type</span>.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">6</td>
<td style="padding: 8px; border: 1px solid #ccc;">Select <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Entire Response</span> for the <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Answer Content</span>.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">7</td>
<td rowspan="2" style="padding: 8px; border: 1px solid #ccc; vertical-align: top;"><span class="uiElement">Routing Configuration</span>
</td>
<td style="padding: 8px; border: 1px solid #ccc;">Do not select <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Require user confirmation before populating other questions</span>. </td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">8</td>
<td style="padding: 8px; border: 1px solid #ccc;">Select <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">JMESPath A JSON query language.</span> for <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Extract answer with</span>. Select the <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">Incident Work Order Number</span> question and use <i xmlns="http://www.w3.org/1999/xhtml">msdyn_name</i> for the <span class="uiElement" xmlns="http://www.w3.org/1999/xhtml">JMESPath Expression</span>.</td>
</tr>
</tbody>
</table>

Learn more about setting up a Webhook, in [Set Up a Webhook](2SetUpWebhooks.md).

### 6. Configure Conditional Logic rules for the form

Conditional Logic controls when the confirmation and incident questions appear, and which values are copied from the existing to the new work order.

<table style="width: 100%; border-collapse: collapse;">
<col style="width: 5%;"/>
<col style="width: 25%;"/>
<col style="width: 70%;"/>
<thead>
<tr>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Step</th>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Trigger</th>
<th style="text-align: left; padding: 8px; border: 1px solid #ccc;">Action</th>
</tr>
</thead>
<tbody>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">1</td>
<td rowspan="3" style="padding: 8px; border: 1px solid #ccc; vertical-align: top;"><span class="uiElement">Show additional questions</span>
</td>
<td style="padding: 8px; border: 1px solid #ccc;">In the <span class="uiElement">Logic</span> section, create a trigger named <span class="uiElement">Show additional questions</span>.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">2</td>
<td style="padding: 8px; border: 1px solid #ccc;">
<p>Set the condition to: </p>
<p><code>qGasReading</code> is greater than <code>RegulatoryThreshold</code>, or <code>qReleaseConfirmed</code> <span class="uiElement">OR</span> <span class="uiElementNotInProcedure">qReleaseConfirmed</span> = <i>Yes</i>.</p>
</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">3</td>
<td style="padding: 8px; border: 1px solid #ccc;">Add the following actions:

                        <ul><li>Set <code>qIncidentDeclared</code> to <i>visible</i>.</li><li>Set <code>qIncidentDeclared</code> to <i>required</i>.</li></ul></td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">4</td>
<td rowspan="3" style="padding: 8px; border: 1px solid #ccc; vertical-align: top;"><span class="uiElement">Incident Reported?</span>
</td>
<td style="padding: 8px; border: 1px solid #ccc;">Create a second trigger named <span class="uiElement">Incident Reported?</span>.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">5</td>
<td style="padding: 8px; border: 1px solid #ccc;">Set the condition to: <code>qIncidentDeclared</code> = <i>Yes</i>.</td>
</tr>
<tr>
<td style="padding: 8px; border: 1px solid #ccc; vertical-align: top;">6</td>
<td style="padding: 8px; border: 1px solid #ccc;">Add the following actions:

                        <ul><li>Set <code>sFollowUpWO</code> <span class="uiElement">(Reportable Incident)</span> section to <i>not ignored</i>.</li><li>Set <code>incidentWOID</code> (the parent work order ID) to <code>parentworkorder_guid</code>.</li><li>Set <code>incidentServAccName</code> (the service account name) to <code>msdyn_serviceaccount</code>.</li><li>Set <code>IncidentCustomerAsse</code> (the customer asset name) to <code>IncidentWorkOrderCus</code>.</li></ul></td>
</tr>
</tbody>
</table>

Learn more by reading [Building Conditional Logic Rules](../Published/115003318126.md)

### 7. Test this recipe end-to-end

Complete the following steps to verify end-to-end that the form, Data Source, Conditional Logic, and Webhook work together correctly.

| Step | Action |
| --- | --- |
| 1 | Deploy the form to a test user and sync the mobile app so the latest form and Data Source configurations are available. |
| 2 | Open the form, select a work order from the Data Source, and verify that the related questions are populated correctly. The work order context questions populate with the corresponding values from Microsoft Dynamics. |
| 3 | Enter gas readings above the regulatory threshold or select Yes for Visible Hydrocarbon Release , and confirm that the incident declaration and Incident Report section appear as expected. The incident declaration question and the Incident Report section become visible. |
| 4 | Confirm a reportable incident and select Run Action on the Webhook question to create the incident work order. Verify that a new incident work order is created in Microsoft Dynamics with the correct incident type. A new incident work order is created in Microsoft Dynamics with the correct incident type and linked parent work order. |
| 5 | Confirm that the identifier for the new work order is parsed from the Webhook response and displayed within the form. The Incident Work Order Number field displays the new work order number returned by Microsoft Dynamics. |

Downloading DynamicsRecipe.md… Go back