Record Does Not Exist in Destination Host Example

This page provides an example for a Power Automate flow from a Microsoft Dynamics 365 CE to a Microsoft Dynamics 365 F&O Sales Order when a record does not exist in the destination host.

Setup

The following setup is required for executing the example flow:

Set up the Aquarium database, available for download here.
The Process Design JSON file is available here.
The SalesOrderNumber field is populated with a number series.

The process structures differ between Microsoft Dynamics 365 CE and Microsoft Dynamics 365 F&O requiring varying levels of complexity. Ensure you put in your connection IDs in the Process Design and the database.

Parameter form

The following settings are essential to launch the Configurator successfully. Users can effectively initiate the Configurator within their specified environment by utilizing these settings. Additionally, users have the flexibility to input environment details according to their specific requirements. These settings ensure a seamless and efficient configuration process tailored to meet individual needs.

Microsoft Dynamics 365 F&O

Navigate to Experlogix Integrator > Experlogix Parameters.

Microsoft Dynamics 365 BC

In the Search bar, search for and select Experlogix Settings.

Microsoft Dynamics 365 CE

Navigate to Settings > Advanced settings > Explerlogix > Settings.

Salesforce

Navigate to the Experlogix App > Connection Settings > Default Settings > Connection ID.

Microsoft Dynamics 365 CE Sales Quote to Microsoft Dynamics 365 F&O Sales Order Flow

The Microsoft Dynamics 365 CE Sales Quote to Microsoft Dynamics 365 F&O Sales Order Flow includes configuring a quote in Microsoft Dynamics 365 CE , creating a header record in Microsoft Dynamics 365 F&O and copying the configuration to Power Automate when the record does not exist in the host. The following example provides the high-level steps.

In Microsoft Dynamics 365 CE, configure a Quote as shown in the following image.
In Power Automate, access the Experlogix Copy Configuration NameVersion flow.
Select Run and enter the following data.

Parameter	Input	Example value	Where to retrieve value from	Mandatory	Remark
Source Entity Name	The entity in the source host	Quote	Process Context in process designer	Yes
Project Name	Name of the integratorData in the integration API			No	If provided, please also provide the 'Integrator Data Document Name' and 'Document version'
Source Record ID	Record ID in the source entity	3ceb1717-985b-ee11-be6f-6045bd006366	See parameter form for more information.
Source Company	Company in source host. Only relevant to FO.		Only applicable to Microsoft Dynamics 365 F&O, is the name of the company
Destination Configuration Name	Configuration name for destination	10c09ffc-4fb2-4ebf-a8eb-bf5157bfb9e3	10c09ffc-4fb2-4ebf-a8eb-bf5157bfb9e3
Destination Configuration Version	Configuration version for destination.	1	1
Destination Company	Company in destination host. Leave the field blank if not required.	USMF	Only applicable to Microsoft Dynamics 365 F&O, is the name of the company
Source Connection ID	Connection ID of the source host.	440c473e-f36b-1410-8b2f-008747a9a79c	See parameter form for more information.	Yes
Destination Connection Id	Connection ID of the destination host.	d8689d24-e011-4f73-b4b3-602a8f2cc5ca
Document version	Version of the integration data. If you don't specify a version, the latest version is used			No	If provided, please also provide the 'Integrator Data Document Name' and 'Project Name'
Index	Index number of the lineitem of the configuration.xml. If left blank, it will process all lineitems			No
Configuration name	Name of configuration
Configuration version	Version of configuration
Integrator Data Document Name	Name of the process-design			No	If provided, please also provide the 'Document Version' and 'Project Name'
Replace	Replace the configuration if it already exists.	true
Process State	Copy the process state. It is not applicable as the scenario is from host A to host B.	false

Select Run.
On the ExperlogixCopy Configuration Flow page, select the ellipsis to open the contextual menu and select Run history.
In Microsoft Dynamics 365 F&O, to view the processing, enable logging for processing.
In Power Automate, access the Experlogix Process Configuration NameVersion flow.
Select Run and enter the following data.

Parameter	Input	Example Data	Where to retrieve the value	Mandatory	Remark
Entity Name	Entity in destination host.	SalesOrderHeaderEntity	Process Context in process designer	Yes
Project Name	Name of the integratorData in the integration API			No	If provided, please also provide the 'Integrator Data Document Name' and 'Document version'
Company	Company in the destination host. Only relevant to FO.	USMF	Only applicable to Microsoft Dynamics 365 F&O, is the name of the company	No
Connection ID	Connection ID of the destination host.	d8689d24-e011-4f73-b4b3-602a8f2cc5ca	See parameter form for more information.	Yes
Document Version	Version of integrationData. If you don't specify a version, the latest version is used .		Please get in touch with Professional Services to find this value	No	If provided, please also provide the 'Integrator Data Document Name' and 'Project Name'
Index	Index number of the lineitem of the configuration.xml. If left blank, it will process all lineitems		Numbering starts at value 0	No
Configuration name	Name of configuration	10c09ffc-4fb2-4ebf-a8eb-bf5157bfb9e3	10c09ffc-4fb2-4ebf-a8eb-bf5157bfb9e3
Configuration version	Version of configuration	Please provide a configuration version, for example 1.	1
Integrator Data Document Name	Name of Process Design.	CPQ_integratorData	hard-coded	No	If provided, please also provide the 'Document Version' and 'Project Name'

Select Run. The Flow history displays the Record ID.

Navigate to the host-logging and disable it.

The various steps of processing are available on the logging page.

Navigate to the destination Record ID and select Configure.

You are now able to reopen the Configuration in the destination host.