Mapping lookup fields from Account to Opportunity

(0) Share

Report

Posted on by Arkady Karasin

Hello All,

Help needed.

I need to map lookup field Partner (target record type is Account) to the similar field in Opportunity. The idea is to pass reseller name from Account to new Opportunity.

I created new_partner fields in Account and Opportunity. In Account 1:N Relationship I created new relationship new_account_opportunity_Partner with Referential type of behavior. In Mappings source Field I can select new_partner, but similar field does not appear in Target Entity Fields.

Question #1: Why target field is not available?

Question #2: In Mappings appear new mapping with source name accountid and target name new_partner. I can't edit it and can't delete. What should I do with this one?

Question #3: How can I delete created relationship new_account_opportunity_Partner ?

Any help is very appreciated!

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

Niamh Stanley on at

Like (0)

Report

Hi!

I would love to try and help. Sorry if these questions are too simple to start. Are your two fields definitely of the same type? And if they are a look up, do they look up the same thing?

If mappings is too confusing, you could make a workflow to run when field changes.

If you create a workflow called something like "FillPartnerInOpportunity" withh target record of account. Set it to run when the new_partner field changes. Set the workflow to update the opportunity record with whatever the account record has filled in the partner field.

I knocked up a quick example in my own CRM, so think of my Business as your opportunity entity and the primary contact as your partner field.

If this needs any more explaining let me know i'm happy to help :)

Please mark as answer if it helped!

Was this reply helpful? Yes No
Niamh Stanley on at

Like (0)

Report

In terms of deleting the relationship, as long as you aren't mapping any fields using this relationship you should simply be able to select the relationship and click the x to delete. The only reason it wouldn't delete would be if it had any dependencies.

Although if you follow my suggestion above, you will need this relationship for the look up field.

Was this reply helpful? Yes No
Arkady Karasin on at

Like (0)

Report

Thank you Niamh, but workflow will not work in my case. The field new_partner in Account not changes. The field in Opportunity should be updated on new opportunity creation. Not when it saved.

Was this reply helpful? Yes No
Niamh Stanley on at

Like (0)

Report

Makes sense!

Is your problem that the new_partner field in the opportunity doesn't show up when trying to map the field from the account entity relationship?

Was this reply helpful? Yes No
Arkady Karasin on at

Like (0)

Report

Question #3 is solved by itself. I just successfully deleted relationship new_account_opportunity_Partner. Probably it just takes a time.

Now I am trying to use existing vanilla relationship new_account_opportunity:

and add new mapping but new_partner not appear:

Was this reply helpful? Yes No
Niamh Stanley on at

Like (0)

Report

Thanks for the screenshots they are very helpful in understanding your problem.

It may be a silly question but did you save and publish after making the field on the opportunity form, sometimes the fields will not show if it was not published?

Any field should show up in the target entity fields regardless of their datatype and if they match

Niamh

Was this reply helpful? Yes No
Arkady Karasin on at

Like (0)

Report

Yes. This is what I expected when created two lookups.

To confirm that everything published I added the new_partner field on Opprtunity form.

May be I should wait? I never meet delays in Dynamics 365.

Was this reply helpful? Yes No
Verified answer

ashlega 34,477 on at

Like (2)

Report

Hi Arkady,

this is just how it works. Since there is an out of the box parental relationship (opportunity_customer_accounts), all those additional account lookups are automatically mapped to that same "parent" (accountid field), and, since they have already been mapped automatically, you can't map them to another field.

You might want to use javascript to implement custom mapping (in the onload of your opportunity form - query the account record, get that partner field from there, and populate corresponding field on the opportunity)

Was this reply helpful? Yes No
Arkady Karasin on at

Like (0)

Report

Thank you, Alex,

I spent some 2 days on this issue... Now your answer made sense!

Javascript option that you suggest, is over my knowledge, I went to workflow option. Update new_partner in Opportunity on creating.

Was this reply helpful? Yes No