If you create a map using Dynamics 365 (CRM) as a target and see the error shown below, it may be caused by populating a field in the target that requires an associated field to also be populated. If the second field upon which the first one depends is either not linked or is being populated by a null or invalid value, the error can occur. For example, Id and IdType fields must be mapped together.

Unable to insert data into the XYZ entity. An unexpected error occurred.
 

Id And Idtype

For Dynamics 365 Target Connections, if you map an id field, such as ownerid or customerid, you may also need to set the corresponding idtype to the value of the id base field ( owneridtype or customeridtype). To determine if you need to map the type field, see the Description of the field displayed by selecting the Info icon (?) for the Entity on the Fields tab. See Block Properties Fields Tab and review the Viewing Field Properties section. 

Ownerid And Owneridtype

For Dynamics 365 target Connections, both the ownerid and owneridtype fields may need to be mapped:

• Create — If you are mapping the ownerid field during a Create or a create through an Upsert, you must also map the owneridtype field. Otherwise, an error occurs and the record is not assigned to any user type.
• Update — If you are performing an Update or an update through an Upsert, mapping the owneridtype field is optional.

NOTE: If you perform an Update or an update through an Upsert, provide an ownerid without an owneridtype, and the ownerid does not match any existing systemuser or team, the following error occurs: systemuser not found.

Example

For example, in the image below, the Description indicates that if you map the ownerid field, you must also set a value for the ownertypeid field.

 

In the image below, the Description for the owneridtype field specifies the possible base entities and values: systemuser, team. To set this value, enter the name of the base field type in quotation marks into the Formula field.

 
Other possible errors caused by not mapping both required fields include:

Error title: Error in calling Operation Update
Error description: One or more post operations failed
Post operation Assign failed for entity: “entity_name” | Id: “guid” | Error: Required member 'LogicalName' missing for field 'Assignee'

For additional information, see the following in TIBCO Scribe® Online Help:

• TIBCO Scribe Online Connector For Microsoft Dynamics 365 / CRM
• Formula Editor

 

Use this article to troubleshoot the following error: Unable to insert data into the XYZ entity. An unexpected error occurred.