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 ServiceNow incidents with Dynamics 365 cases 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

.

The caller from ServiceNow searches for contacts in Dynamics 365. If the contact is not found, a contact is created even though an account with the same name exists.

The owner is searched by email ID. If the email ID is not found, the process assigns the default API owner. For example,

MSDynamicsAPI

. 

The owner in Dynamics 365 can only be a system user. Otherwise, the process assigns the default owner.

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>