Fixed – ‘The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId’ error while processing Email Attachment using SSIS

By | September 8, 2017

Introduction:

While performing data migration most of the time, we need to migrate Email and Email Attachments, where we first migrate the Emails and then migrate the Email Attachments.

However, when we did a run for this, we were facing the below error.

‘The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId.’

We had done the mapping for the Email attachments in the Destination CRM as shown in the screenshot below;

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

After investigating into this error, we found that we need to map either of the below fields.

ActivityId OR ObjectId and ObjectTypeCode

So, when we removed the mapping of the fields ‘ObjectID’ and ‘ObjectTypeCode’ from the mapping in the target CRM component, we did not get any error!

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

This time the attachments migrated successfully to the Target CRM.

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

Email in Source CRM:

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

Email in Destination CRM:

'The attachment cannot be saved. Either specify activityId or ObjectTypeCode & ObjectId' error while processing Email Attachment using SSIS

Conclusion:

While either migrating or creating an attachment to CRM you need to map either ‘ActivityId’ Or ‘ObjectId’ and ‘ObjectTypeCode’.

Get started with QuickBooks and Dynamics 365 Integration

Leave a Reply