Wednesday, 19 April 2023

{How to} Resolve Relationship Mapping fields between Opportuntiy and Quote entities Dynamics 365 Sales

Hello Everyone,

Hope everyone doing good.


Today i am going to share simple OOTB feature which some of them aware but i want to bring this to my blog readers.


Scenario: Suppose there is a requirement to transfer some data from Opportunity to Quote when an Opportunity is qualified automatically. 


Like When a lead is qualified some of the data will be automatically transferred to Opportunity, do you know how this is happening without any code written, its because of "Relationship Mapping" from the 1-N relationship between entities.



Lets see this in action.


So for this example i have created a business unit lookup field on the Opportunity entity, and also on the Quote entity same business unit lookup field is created.


Now i want to carry same field value of business unit of Opportunity to business unit of Quote.


Create a solution and add the opportunity and quote to it.


Steps taken:


1. Create a business unit lookup field on the opportunity


make sure select the target entity for the business unit field as 'BUSINESS UNIT' 


2. Similarly create the business unit lookup field on the Quote entity too, same as step 1.

3. Create a Relationship mapping. 




4. Once Opportunity and Quote relationship selected, you need to open the relationship and click on the "mapping" on the left side of the screen, 

Then mapping the fields like below screenshot.




5. Publish the changes on the solution.


6. Create an Opportunity fill the "busiess unit" as UK and qualify the  Opportunity






As you can see from the above screen when you qualify the opportunity prompt to create a  Quote.



Now you will see the Business unit has a value as UK on the next screen.





So its that simple to add relationship mapping and OOTB field mapping between the entities.

For more information please visit Microsoft Docs


I hope this helps.

Malla Reddy(@UK365GUY)
#365Blogpostsin365Days



















No comments:

Post a Comment

Note: only a member of this blog may post a comment.