Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
The nature of my use case is such that the processes like Opportunities and Quotes requires static details from Contact for a few reasons,
1. The details of the person in Contact may affect the price. Example: Occupation at the point of quote generation is Doctor versus a year later the same person may be a retiree.
2. For audit purposes. Example, When we review the Quote 1 year later, the Occupation should reflect as Doctor at the time of quote generation which is a Doctor and not now (according to his updated Contact - retiree).
I had originally used Contact Lookup Field to populate a Quickview Form, but it won't work correctly as the information in the Opportunity and Quotes would then change as the Contact record gets updated.
Therefore, I have created Fields to capture these values at the time of the quote so they would remain static and wouldn't change as the Contact record gets updated. Is this the correct way to handle such situation? Is there any other better ways to do it?
Thank you for your query.
In my opinion, this is the right approach.
In some scenerios, we create a seprate entity for this purpose, for example, Freight Info.
Freight Info would have an lookup to Order. We would copy terms from Account,. The reason for creating a separate entity is because we have freight lines as well linked to freight info.
However, in your scenario, you can add fields directly in the quote, that makes sense.
Business Applications communities