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 :
Microsoft Dynamics CRM (Archived)

Can't change a mapping in a relationship

(0) ShareShare
ReportReport
Posted on by

Hi all:

I am probably missing something really basic, but am stumped on this:  I need a lookup from Opportunity to map to Order.  If I create the new field as a lookup, it will create a mapping from "opportunityid" to "order_custom_field" but I cannot delete this mapping, nor can I add a mapping of "opp_custom_field" to "order_custom_field" as that field is already mapped.

What am I missing here?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    on at

    Are you trying to put the lookup to Opportunity from Order? Doesn't the lookup require the opportunityid to link correctly?

  • rmcanally65 Profile Picture
    on at

    Nathaniel:

    I am going Opp to Order.  What I need is to have a mapping from an (existing) lookup field in Opp to another (new) lookup field in Order.  But when I create the new field in Order, the mapping is created as above, which means I can't map anything else to this new field.

  • Verified answer
    Paige Cassada Profile Picture
    on at

    Rob,

    As you know the nature of creating a lookup means creating a field that when clicked on shows a list of records from which to choose. In your case it you created a custom lookup field and you are using that to lookup an opportunity. End result being you will see an opportunity link on your order in a custom field.

    If you would like to create something that maps the value on an opportunity to an order when the order is created from the opportunity, say a text value, then you would add that type of mapping to the 1:N relationship between opportunity and order.

    It is unclear why you want to create a lookup to an opportunity but then delete it because then they would no longer be linked. Maybe a scenario or user story might clarify for us.

  • Verified answer
    Community Member Profile Picture
    on at

    I believe the best thing you can do is, instead of creating a lookup field is, just create the relationship and then on the form create a subgrid, in the subgrid you specify the entity you want to show (orders, i believe) and select to show only related records.

  • Verified answer
    Aileen Gusni Profile Picture
    44,524 on at

    Hi Rob what is the existing lookup field name from Opportunity entity? Is this a system field one?

    Thanks

  • rmcanally65 Profile Picture
    on at

    Thanks, Joao (and everyone else)!

    I think the subgrid option is probably best for us at the moment.

  • Aileen Gusni Profile Picture
    44,524 on at

    Hi Rob

    If possible using the oob subgrid.

    Sorry dont really get what relationship you are referring to.

    Or if not then another choice is using the html web resource.thanks

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 > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans