Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
If you have ever worked with the Dynamics CRM Opportunity, you know that it contains a function to recalculate the opportunity when you have selected System Calculated for the Revenue.
Here are the major areas of focus for this discussion:
When the user presses the Recalculate button on the Ribbon, all of the associated line items will be summaries and that number placed into the Est. Revenue field (estimatedvalue is the internal field name).
If you add an OnChange event to the Est. Revenue field, it will not be fired by the Recalculate Opportunity button. This is because the value of this field is not modified on the form, it is modified in the database.
If you have selected User Provided for the Revenue field, the Est. Revenue field becomes editable and the OnChange event will fire, after someone changes the value and leaves the field.
When a user clicks the Recalculate Opportunity button, the following events will occur, in this order:
You just finished reading Recalculate Opportunity and the Page Life Cycle! Consider leaving a comment!
Follow me on Twitter @mitchmilam. Read my new book: Dynamics Deep Dive: Security
Business Applications communities