You must use the same Secure Agent to configure the app connections and processes that are packaged in the recipe.

You must first configure the connections in the recipe and publish them before opening or updating the process. Otherwise, the process will contain empty fields from the connections and will become invalid.

Informatica recommends that you use the same names configured for the assets in the recipe. If you use the same asset names, you can publish all the assets and synchronize the data from Dynamics 365 cases with ServiceNow incidents without any issue. However, if you change the names, you must ensure that you update the names in the related fields in other assets.

If the tenant already contains connections with the same name as the connections added from the package, the process in the recipe becomes invalid. This is because the newly added connection name contains the suffix

-2

. For example,

<connection_name>-2

.

Synchronization of Dynamics 365 case to ServiceNow incident is performed on the assumption that the customer in Dynamics 365 is Contact Type. The Dynamic 365 cases with accounts as a customer does not synchronize and return failed case number in email.

When a case contains a customer with contact, and not the email, the caller in ServiceNow displays the system user that does not have email defined.

To handle Integer and Double data types correctly and ensure proper behavior in the Dynamics 365 connection, you must specify annotation attributes or additional parameters in the request as shown in the following sample:

<account 
xmlns:m="urn:informatica:ae:xquery:json2xml:meta-data">
<name>test name</name>
<telephone>000-111-22-33</telephone>
<emailaddress>account@test.com</emailaddress>
<fax>123-456</fax>
<revenue 
m:type="xs:double">1000.50
</revenue>
</account>

<account 
xmlns:m="urn:informatica:ae:xquery:json2xml:meta-data">
<name>test name</name>
<telephone1>000-257-35-89</telephone1>
<fax>547-890</fax>
<versionnumber 
m:type="xs:int">1</versionnumber>
</account>