Create an intake provider

15 minutes

This unit describes the steps that are required for creating an intake provider in Intelligent Order Management.

Add new providers

There are multiple providers available in Dynamics 365 Intelligent Order Management that your organization can leverage to optimize business processes. Providers allow you to seamlessly connect external systems to Intelligent Order Management.

For more information on the providers available in Dynamics 365 Intelligent Order Management, go to Provider Catalog.

Create a new provider definition

To create a new provider definition, follow these steps:

Go to Providers > Catalog.
Select New Provider Definition.
For Display Name, enter LabOrderIntakeProvider.
For Logical Name, enter msdyn_LabOrderIntakeProvider.
For Logo, select Lab.png.
For Service Type, enter Order intake.
For Description, enter Lab order intake provider.
Select Save & close.

Add a provider definition to a solution

To add a provider definition to a solution, follow these steps:

Go to Power Apps maker portal and go to the newly created LabProviders solution.
Select Add existing > Provider Definition.
Select LabOrderIntakeProvider and then select Add to add it to the solution.

Add a transformation to the provider definition

To add a transformation to the provider definition, follow these steps:

Go to Providers > Catalog.
Select the newly created LabOrderIntakeProvider.
Select Edit on the menu bar.
Select the Transformations tab.
Select + New IOM Provider Definition Transformation.
For Display Name, enter Lab Order to Dataverse Order.
For Logical Name, enter msdyn_LabOrderIntake_Order.
For Provider Definition, enter or select LabOrderIntakeProvider.
For Source Object Name, enter LabOrderIntakeProvider.
For Destination Object Name, enter Dataverse Order.

For Transformation, paste in the following M query code:

 shared ImportMappingKey = [
account = {
 		[
 			ExternalRecordKey = [ProviderName = "LabOrderIntakeProvider"],
 			SelectedFields = {"accountid"}
 		]
},
 	pricelevel = {
 		[
 			ExternalRecordKey = [ProviderName = "LabOrderIntakeProvider"],
 			SelectedFields = {"pricelevelid"}
 		]
},
 	product = List.Distinct(List.Transform(Source[orderdetails], each
 		[
 			ExternalRecordKey = [sku = _[sku]],
 			SelectedFields = {"productid"}
 		])),
 	uom = List.Distinct(List.Transform(Source[orderdetails], each
 		[
 			ExternalRecordKey = [unit = _[unit]],
 			SelectedFields = {"uomid"}
 		]))
];
shared TransformSourceData =
let
 orderProducts = Source[orderdetails],
 account = IOM.MapRecord(IOM.MappingTables[account], [ProviderName = "LabOrderIntakeProvider"]),
 pricelevel = IOM.MapRecord(IOM.MappingTables[pricelevel], [ProviderName = "LabOrderIntakeProvider"]),

 orderheader = Record.FromTable
 				(
 					Table.SelectRows
 					(
 						Record.ToTable
 						(
 							[
 								ordernumber = Text.From(Source[ordernumber]),
 								name = ordernumber,
 								#"customerid_account@odata.bind" = "/accounts(" & Text.From(account[accountid]) & ")",
 								#"pricelevelid@odata.bind" = "/pricelevels(" & Text.From(pricelevel[pricelevelid]) & ")",
 								billto_city = Record.FieldOrDefault(Source, "billtocity"),
 								billto_stateorprovince = Record.FieldOrDefault(Source, "billtostateorprovince"),
 								billto_country = Record.FieldOrDefault(Source, "billtocountry"),
 								billto_postalcode = Record.FieldOrDefault(Source, "billtozip"),
 								shipto_city = Record.FieldOrDefault(Source, "shiptocity"),
 								shipto_stateorprovince = Record.FieldOrDefault(Source, "shiptostateorprovince"),
 								shipto_country = Record.FieldOrDefault(Source, "shiptocountry"),
 								shipto_postalcode = Record.FieldOrDefault(Source, "shiptozip")
 							]
 						), each [Value] <> null
 					)
 				),

 orderlines = List.Transform(orderProducts, each
 					Record.FromTable
 					(
 						Table.SelectRows
 						(
 							Record.ToTable
 							(
 								[
 									ispriceoverridden = true,
 									#"productid@odata.bind" = "/products(" & IOM.MapRecord(IOM.MappingTables[product], [sku = Record.FieldOrDefault(_, "sku")])[productid] & ")",
 									#"uomid@odata.bind" = "/uoms(" & IOM.MapRecord(IOM.MappingTables[uom], [unit = Record.FieldOrDefault(_, "unit")])[uomid] & ")",
 									quantity = [quantity]
 								]
 							), each [Value] <> null
 						)
 					)
 				),

 salesorder = Record.AddField(orderheader, "order_details", orderlines)

 in Text.FromBinary(Json.FromValue(salesorder));

For Transformation Source Type, enter JsonPayload.
Select Save.

Create a JSON file, paste in the following code, and then save it.

{
  "ordernumber": "LabOrder001",
  "shiptocity": "BELLEVUE",
  "shiptostateorprovince": "WA",
  "shiptocountry": "US",
  "shiptozip": "98007",
  "billtocity": "BELLEVUE",
  "billtostateorprovince": "WA",
  "billtocountry": "US",
  "billtozip": "98007",
  "orderdetails": [
{
  "sku": "883988211855",
  "unit": "each",
  "quantity": 11
}
  ]
}

Next to the Sample Data field, select Choose File and then upload the JSON file that you created.
Select Save & close.

Add a provider definition transformation to a solution

To add a provider definition transformation to a solution, follow these steps:

Go to Power Apps maker portal and go to the newly created LabProviders solution.
Select Add existing > Provider Definition Transformation.
Select Lab Order to Dataverse Order, and then select Add to add it to the solution.

Create a provider message handler

To create a provider message handler, follow these steps:

Go to Power Apps maker portal, go to Solutions, and then open the Default Solution.
Select New.
Select Cloud Flow and then name it Lab Order Intake Message Request Handler.
Select the trigger type as Outlook.com – When a new email arrives (V2), and then sign in with your outlook.com account credentials.
For Folder, select Inbox.
For To, select Recipient email addresses separated by semicolons.
For CC, select CC recipient email addresses separated by semicolons.
For To or CC, select To or CC recipient email addresses separated by semicolons.
For From, select Sender email addresses separated by semicolons.
For Include Attachments, select Yes.
For Subject Filter, select LabOrderIntakeOrder.
For Importance, select Any.
For Only with Attachments, select Yes.
Select New step and then add parse json.

For Content, paste in the following code:

{
"ProviderId": "00000000-0000-0000-0000-000000000000"
}

Select Generate from sample and then paste in the following sample schema code:

{
  "type": "object",
  "properties": {
    "ProviderID": {
      "type": "string"
    }
  }
}

Select Done.
Select the ellipsis (...) and then select Rename.
Rename the action IOM System Properties.
Select Save.
Select New step, add a Parse JSON action, and then rename it to Initialize Provider Variables.

For Content, paste in the following code:

{
  "SourceObjectName": "IOMLab Order",
  "DestinationObjectName": "Dataverse Order"
}

Select Save.
Select New step, add an Initialize variable action, and then rename it to Initialize Processing Execution Result.
For Name, enter ExecutionResult.
For Type, select Boolean.
For Value, select true.
Select Save.
Select New step, add scope, and then rename it to Try.
In the Try scope, select Add an action.
Add perform an unbound action from the Dataverse connector and then rename it to Acknowledge the Provider Message.
For Action Name, enter msdyn_CreateProviderMessageRequestExecution.
For PowerAutomateWorkflowId, enter workflow()['tags']['xrmWorkflowId'] as an expression.
For PowerAutomateRunId, enter workflow()['run']?['name'] as an expression.
For ProviderExternalRequestId, enter guid() as an expression.
Select Save.
Select Add an action and then add an Apply to each control.
For Select an output from previous steps, select Attachments.
Select Add an action within the Apply to each loop, add Run a child flow from the Flow connector, and then rename it Transform Message with Power Query Online.
For Provider Id, select the ProviderId variable.
For Source Object Name, select the SourceObjectName variable.
For Destination Object Name, select the DestinationObjectName variable.
For Payload, enter decodeBase64(items('Apply_to_each')?['ContentBytes']) as an expression.
Select Save.
After the transformation step, select Add an action, add Run a child flow from the Flow connector, and then rename it Create Order.
For Child Flow, enter Sales Order Creation.
For Payload, enter string(json(outputs('Transform_Message_with_Power_Query_Online')?['Body']?['result'])?[0][0]) as an expression.
Select Save.
Collapse the Try scope by selecting its title bar.
Select New step, add a scope, and then rename it Catch.
In the Catch scope, select the ellipsis (...) and then select Configure run after.
Select the has failed and has timed out checkboxes and then select Done.
In the Catch scope, select Add an action, add a Set variable action, and then rename it Set the execution result to failed.
For Name, enter ExecutionResult.
For Value, select False.
Select Save.
Collapse the Catch scope by selecting its title bar.
Select New step, add a scope, and then rename it to Finally.
In the Finally scope, select the ellipsis (...) and then select Configure run after.
Select the is successful, has failed, is skipped, and the has timed out checkboxes. Select Done.
In the Finally scope, select Add an action, add Perform an unbound action, and then rename it to Save Provider message request execution result.
For Action Name, enter "msdyn_UpdateProviderMessageRequestStatus".
For ProviderMessageRequestExecutionId, enter @outputs('Acknowledge_the_Provider_Message')?["body/ProviderMessageRequestExecutionId'].
Select Save.

Add a provider definition logic definition to the provider definition

To add a provider definition logic definition to the provider definition, follow these steps:

In your Intelligent Order Management application, go to Providers > Catalog.
Select the newly created LabOrderIntakeProvider.
Select Edit on the menu bar.
Select the Logic definitions tab.
Select + New IOM Provider Definition Logic Definition.
For Display Name, enter Lab Order Intake Message Request Handler.
For Logical Name, enter msdyn_LabOrderIntakeMessageRequestHandler.
For Provider Definition, enter LabOrderIntakeProvider.
For Logic Type, enter Provide Message Handler.
For Workflow Name, enter Lab Order Intake Message Request Handler.
For Timeout Minutes, enter 2.
For Max Retry Attempts, enter 3.
For Description, enter Lab Order Intake Message Request Handler.
Select Save. This step will generate a JSON representation of the message handler cloud flow and will fill in the Client Data field.
Select Save & Close.
Select Connections. The Microsoft Dataverse and Outlook.com connection reference definitions should be listed.

Note

If connection reference definitions other than Microsoft Dataverse and Outlook.com display, it means that you are using more than one Dataverse connection reference in your order intake message handler flow. To fix this issue, go to your flow and ensure that all Dataverse actions are using the same connection reference.

Add a provider definition logic definition to the LabProviders solution

To add a provider definition logic definition to the LabProviders solution, follow these steps:

Select Add existing > Provider Definition Logic Definition.
Select Lab Order Intake Message Request Handler and then select Add to add it to the solution.

Add a provider definition connection reference to the LabProviders solution

To add a provider definition connection reference to the LabProviders solution, follow these steps:

Go to Power Apps maker portal and go to the newly created LabProviders solution.
Select Add existing > Provider Definition Connection Reference.
Select the Microsoft Dataverse and Outlook.com connection reference definitions and then select Add to add them to the solution.

Continue