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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
The use case is we have 12 custom fields that are entered into a sale opportunity that also need to be part of quotes. I had originally used the field mapping function until I discovered that the way field mapping works is that the data from the opportunity fields is COPIED to the Quote fields, but then if the data is updated on the opportunity after the quote is created the mapped field IS NOT updated to the quote.
So now I'm just going to look instead of mapping using a calculated field in the Quote to display the custom field data from the parent Opportunity.
We don't need to edit the custom field data at the Quote entity, we only need to display it on the forms and pdfs.
Just wanted to know if the calculated fields is the best way to go in this situation. I was not finding a lot of information on the use case of having to display data from the parent entity on the related child entity.
As for me it's better to use "Quick View" form instead.
Thanks Andrew, I have not setup a quick view yet and I just realized I was making the assumption that I couldn't pull the custom opportunity fields into a pdf if I used the Quick View... HOWEVER, I realized when reading your suggestion that 'of course' all of the parent opportunity fields are available through the relationship. I'm going to give the Quick View a try I think that will exactly meet my needs.
Business Applications communities