MS Dynamics 365 CRM
      Back to home
      1. snapADDY Knowledge Base
      2. CRM Integrations
      3. MS Dynamics 365 CRM

      Known solutions for Microsoft Dynamics CRM

      Error Message: Campaign With Id = d7e9...xyz...dc1 Does not Exist

      • Solution: The campaign with this ID is not a valid campaign within Dynamics. Confirm the Record ID of the campaign within Dynamics and update the ID Number in the Visit Report Settings.

      Error Message: The length of the 'jobtitle' attribute of the 'contact' entity exceeded the maximum allowed length of '100'

      • Solution: The field in Dynamics allows a maximum 100 characters. Reduce the lenght of data being exported from snapADDY to Dynamics.

      Error Message: Error processing request stream. The property name 'Value' specified for type Microsoft.Crm.Sdk.Data.Services.EntityReference' is not valid. 

      • Solution: The mapped field is not correct. Please check the lower and upper cases in the API name of the field. The field definition could help you figure out, what is the right name of your field.

      Error Message: Incorrect type of attribute value System.Data.Services.Serializers.JsonReader+JsonObjectRecords

      • Solution: The exported data type from snapADDY does not match the target field data type in Dynamics. A remapping of the field is in this case generally necessary. Please contact us.

      Error Message: Error processing request stream. Error encountered in converting the value from request payload for property 'Value' to type 'Int32', which is the property's expected type.

      • Solution: Source and target field data types do not match. Remapping of that field is necessary. Please contact us and send us the error message.

      Error Message: Error processing request stream. Error encountered in converting the value from request payload for property 'Id' to type 'Guid', which is the property's expected type.

      • Solution: Source and target field data types do not match. Remapping of that field is necessary. Please contact us and send us the error message.

      Error Message: Cannot convert undefined or null to object

      • Solution: Export mapping must be configured. Please contact us and send us the error message.

      Error Message: [{"name":"Error","message":"SecLib::AccessCheckEx2 failed. Returned hr = -2147187962, ObjectId: 9x9999x9-9999-e9xx-9900-009099a99xxx, OwnerId: 22222xx-9bb9-x999-909x-0090999x999, OwnerIdType: 9 and CallingUser: dd4e7b8a-3b96-e811-8117-005056a4b71d, CallerBusinessId: be3139ef-4a1e-e511-a08f-005056a47152. ObjectTypeCode: 4, ObjectBusinessUnitId: 3cf39f0d-f6c7-e311-90cf-005056a43c3e, AccessRights: ReadAccess. Computed rightsToCheck=ReadAccess, grantedRights=8, hsmGrantedRights=None, grantedRightsWithHsm=8.","stack":"Error: SecLib::AccessCheckEx2 failed.

      • Solution: The security privileges within Dynamics are not sufficient to carry out the action. Please verify the security roles for the affected user within Dynamics Security.

      Error Message: Type Mismatch: Type of Attribute: Contact.rcc_nldjd is: System.Boolean. However, Type of passed-in value is: System.Data.Services.Serializers.JsonReader+JsonObjectRecords 

      • Solution: The exported data type from snapADDY does not match the target field data type in Dynamics. A remapping of the field is in this case generally necessary. Please contact us.

      Error Message: Error processing request stream. The request should be a valid top-level resource object.

      • Solution: A particular "Value" is not being exported correctly. The mapping needs to be configured. Please contact us and send us the error message.

      If you have trouble connecting to your MS Dynamics after migrating from one tenant to another please follow this article 👉 error after migrating MS Dynamics