Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Unable to map values u...
Microsoft Dynamics CRM (Archived)

Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

(0) ShareShare
ReportReport
Posted on by Huzefa Bootwala 310

Facing an issue related to OptionSet Mapping.

I want to map the accounts ownership from CRM 2013 to Dynamics CRM 365. I tried mapping ownershipcodename from source to ownershipcode in destination. (This was the only option I got for mapping). It gives the following error as shown below.

I tried mapping Public to Public field but it did not accept it.

I am using Dynamics OptionSet Mapping. Even I thought the same thing that ownershipcodename would be the label. I tried mapping the label value with the label in destination.

Eg: 1 maps to Public

     2 maps to Private etc.

I cant map the labels from source with the labels in destination.

Eg: When I map Public to Public, it gives an error message that both the fields are same.

*This post is locked for comments

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Ohh Ok, now I understood why the transfer shows an error.

    Owner id of both the systems should be the same only then it will look it up.

    Is there a way where I can set the owner id of BackupSVC from CRM 2013 same as that of Dynamics 365? I am not sure of how to make a user mapping table.

    And I will try the test which you mentioned above if I can figure it out.

  • Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    I understand that, but you are trying to set the owner id. That is a lookup to either a user or team record.

    When you set the owner id (which is the BackupSVC user in the 2013 environment) it has to match to the owner id (BackupSVC user in 365). The Guid of BackupSVC user in 2013 is not the same as the Guid of the BackupSVC user in 365.

    I hope that is clear.

    If you want to try a test:

    Retrieve the Accounts from CRM 2013 that have the owner set tp BackupSVC.

    Create a DerivedColumn called targetOwnerId that has a Guid of the BackupSVC from 365 (you will need to open the user record and get the Guid from it), and a column called targetOwnerType that will have a value of "systemuser"

    Set the Destination CRM component, and in the owner id and owner id type attributes set the values from the Derived columns.

    This should most likely work.

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    I am not mapping users. Users already exist in the system. I am migrating the accounts from CRM 2013 to Dynamics 365. All the accounts associated with all the users are working fine except for this one which is BackupSVC which I created before some time.

  • Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    The mapping that I mentioned will only work for options sets, not owner or lookup controls.

    In order to map users you need to use the Guid of the owner record, which is why I said that you will need some sort of a mapping table.

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Yes I am aware of that. I am mapping owneridname from source to ownerid in destination which was mentioned by you.

    I can migrate other users info but this user is showing error. Both have security roles assigned to them.

  • Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Hi,

    The issue is most likely that the Guid of the same user in Dynamics 2013 and Dynamics 365 is different, so the system cannot map the user from one system to another.

    I think I mentioned this previously when migrating owners, that you would probably need a mapping table.

    Can you check if the user with the Id in the error message exists in the new environment?

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Error5.JPG

    Hello,

    There is a user in Dynamics 365 known as BackupSVC#. I created a new user in CRM 2013 with the same name and have assigned a role of Salesperson which has Read privileage on the Account entity. Why does it give an error when transferring accounts from CRM 2013 to 365? Is the Principal user different than the system user?

    This might be a small error so dont want to open a new thread.

  • Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Thanks. Good news. That would cause that error message. :)

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Hello,

    The issue is resolved. Custom Option in source had a different value as compared to the destination. Therefore, it was showing the error.

    Thank you.

  • Huzefa Bootwala Profile Picture
    Huzefa Bootwala 310 on at
    RE: Unable to map values using Dynamics CRM OptionSet Mapping in SSIS

    Yes, this is what I meant in my previous comment.

    I do have ownershipcode in my source and I tried mapping ownershipcode from source to ownershipcode in destination without using OptionsSet Mapping. When I run this, it gives the error which is posted above.

    Is this anywhere related to the security roles of the user? The roles of the users are not fully customized at the moment.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,407 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans