Create an Incident Work Order in Microsoft Dynamics

Note: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.

{
	"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
}

Note: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.

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.

Result: The Dynamics POST webhook is now available to add to forms in your FormSpace.

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

Note:Add Hidden on Device and Read only Restrictions to ID questions.

Note:If question labels are specified, make sure to use them exactly as written, so they match the response body.

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.

• 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.

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.

Note:An alternative is to execute a separate GET request to Dynamics, to return the GUID for the Incident Type selected in the form.

• 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.

• service_account_guid from the Service Account ID question.
• customer_asset_guid from the Customer Asset ID question.
• incident_type_guid from the Incident Type GUID question.

Set the condition to:

qGasReading is greater than RegulatoryThreshold, or qReleaseConfirmed OR qReleaseConfirmed = Yes.

• Set qIncidentDeclared to visible.
• Set qIncidentDeclared to required.

• Set sFollowUpWO (Reportable Incident) section to not ignored.
• Set incidentWOID (the parent work order ID) to parentworkorder_guid.
• Set incidentServAccName (the service account name) to msdyn_serviceaccount.
• Set IncidentCustomerAsse (the customer asset name) to IncidentWorkOrderCus.

Deploy the form to a test user and sync the mobile app so the latest form and Data Source configurations are available.

Open the form, select a work order from the Data Source, and verify that the related questions are populated correctly.

Result: The work order context questions populate with the corresponding values from Microsoft Dynamics.

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.

Result: The incident declaration question and the Incident Report section become visible.

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.

Result: A new incident work order is created in Microsoft Dynamics with the correct incident type and linked parent work order.

Confirm that the identifier for the new work order is parsed from the Webhook response and displayed within the form.

Result: The Incident Work Order Number field displays the new work order number returned by Microsoft Dynamics.