web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

PickListMappingSet: not unique relation between SourceValue and TargetValue

(0) ShareShare
ReportReport
Posted on by 1,788

How does it come that the records of our PickListMappingSet doesn't have a unique relation within single option sets between SourceValue and TargetValue for ~67% of the option sets?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Andreas Cieslik Profile Picture
    9,267 on at

    I assume it is because of global option sets that share values.

  • moko33 Profile Picture
    1,788 on at

    I'm not sure if this is the reason but I don't think so.

    As already mentioned, when querying this in Power Query: XRMServices/2011/OrganizationData.svc/PickListMappingSet?$select=ColumnMappingId,SourceValue,TargetValue I don't get unique relations.

    Example:

    On contact entity in default solution we have a global option set with two possible values 10.000.000 meaning A and 10.000.001 meaning B.

    In PickListMappingSet I get two rows for this option set: 10.000.000 meaning C and  10.000.000 meaning D

    =>Neither C nor D is existent in current default solution.

    => 10.000.001 is completely missing

    Expanding the query further I recognize ColumnMappingId.Name (=Option Set Name, more specific: the display name of the field showing the Option Set SourceValue on the form) & ColumnMappingId.Id being the same and also PickListMapping_ColumnMapping.TargetEntityName being "contact".

    It seems to me that C and D in PickListMappingSet came from a failed data import via data import wizard. However these values are not existent in customization area of the default solution.

    So what's wrong?

    It looks to me that querying "PickListMappingSet?$select=ColumnMappingId,SourceValue,TargetValue" is totally unappropriate to map existing OptionSet Values.

  • Suggested answer
    Andreas Cieslik Profile Picture
    9,267 on at

    I believe there is a bug or missing product feature here:

    ideas.dynamics.com/.../1686453

    Looks like it describes what you experience.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans