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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Mapping Product option set field with Opportunity Product option set field doesn't work

(0) ShareShare
ReportReport
Posted on by 40

Hello,

I'm trying to get the two custom created option set fields mapped. The field should be filled manually in the Product entity, when a new product is beeing created. Then when creating a new opportunity and adding an existing product, the value of the prdocut should be mapped there also. But it seems it doesn't work.

I followed this guide, step by step, https://community.dynamics.com/crm/b/powerxrmblog/posts/how-to-map-option-set-fields-in-crm

I created two new custom option set fields in Product entity and Opportunity entity with the "Use Existing Option Set" to yes.

Any ideas what I'm missing? We are running on-premise with version 8.2

Thank you!

I have the same question (0)
  • Suggested answer
    meelamri Profile Picture
    13,216 User Group Leader on at

    Hello, 

    When you are using mapping, data will only be copied from source to target when you create the one record from the other.

    So mapping will not work in your case. You need a process. 

    Please read this blog: 

    itsolutions.bdo.ca/.../

  • david.abax Profile Picture
    40 on at

    Hi,

    thank you for your reply.

    Why doesn't it work? The product has a value in the custom field there. When I add a product in an opportunity, the value of custom field doesn't get mapped or copied from the source.

    Also when I try to create a new workflow/process; when I want to add a step to update the record, I can not update within the Opportunity Product entity.

    0876.Unbenannt.PNG

  • meelamri Profile Picture
    13,216 User Group Leader on at

    Hi,

    Sorry, maybe I misunderstood your use case. Can you please provide some screenshots ?

  • david.abax Profile Picture
    40 on at

    In the Product entity (source), I made this new custom field as Option Set with Use Existing Option Set to Yes.

    In the Opportunity entity (target), I also made the same custom field with the same set up as above.

    5238.Unbenannt1.PNG

    In the Product entity (source) I created an additional Refential 1:N relationship and made the mappings there too.

    3681.Unbenannt2.PNG

    pastedimage1582114465664v1.png

  • meelamri Profile Picture
    13,216 User Group Leader on at

    So you want to have the same optionSet value in your opportunity product ?  

  • david.abax Profile Picture
    40 on at

    Yes, the value will be entered once in Product.

    Everytime when the product is added as an opportunity product, this value should be automatically copied/mapped.

  • meelamri Profile Picture
    13,216 User Group Leader on at

    I will replay your scenario, I will give you a feedback ASAP.

  • david.abax Profile Picture
    40 on at

    It seems that the mapping between Product and Opportunity Product is not supported generally.

  • Suggested answer
    Paul_Owen Profile Picture
    2,027 on at

    It won't work because an Opportunity Product is a child record of an Opportunity not of a Product. The reason you can't access it in a workflow is because a lot goes on behind the scenes to provide Microsoft's intended functionality so you they restrict what you can do to avoid breaking it.

    Mapping will only work for example like converting a lead to an opportunity it also creates an Account and Contact and you can map any Lead field to any of the same fields on those entities, your custom field is on Product, you are not creating a new product when you create an Opportunity Product hence why it doesn't work.

    Regards

    Paul

  • david.abax Profile Picture
    40 on at

    Thank you for your reply,

    do you have any workaround solution for this to get it work?

    Mapping doesn't work, workflow doesn't work and even business rules can't handle this with setting up a condition to check the value of the source field.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 74 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 31 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans