web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Opportunity: Pricing E...
Microsoft Dynamics CRM (Archived)

Opportunity: Pricing Error - Detail Error

(0) ShareShare
ReportReport
Posted on by LMP 680

Hi Experts,

Our user are unable to set the value of Est. Revenue field. I checked the Audit History and I found this "Pricing Error" field that gets updated from Detail Error to None then gets updated again from None to Detail Error and it removes the Est. Revenue value ($5,000,000.00) that user set.

Anyone encountered this issue?

Appreciate any help on this.

OpportunityPricingError.png

*This post is locked for comments

I have the same question (0)
  • Verified answer
    StefanS365 Profile Picture
    StefanS365 3,575 Most Valuable Professional on at

    Hi there,

    Did you(r user) select a price list?

    And what is the setting of the Revenue field: System calculated or User Provided?

  • LMP Profile Picture
    LMP 680 on at

    Hi Stefan,

    The Est. Revenue field is the out of the box of Opportunity. It is a currency - simple type field.

    We have another Estimated Revenue field and its the same type, currency simple.

    On the Opportunity form we have a Delivery Team subgrid. When you add Delivery Team, the Turnover (Currency - simple) field is required. When a Delivery Team record is created or updated, a plugin will run and sum the Turnover of all Delivery Team associated to the Opportunity then set that value to Est. Revenue field (the OOTB) then a workflow will copy the value of Est. Revenue (OOB) field to Estimated Revenue (custom).

    Out issue is Pricing Error gets updated then it sets the value of estimated revenue to 0.

    I really appreciate the help.

    Opp.-Pricing-Error.png

  • Suggested answer
    LMP Profile Picture
    LMP 680 on at

    I was able to identify the cause of this issue. It was because the Revenue (OOB) field was set to System Calculated instead of User Provided.

    I would like to thank Raz Dynamics, I saw his very helpful post on this thread community.dynamics.com/.../192169

  • StefanS365 Profile Picture
    StefanS365 3,575 Most Valuable Professional on at

    Hi,

    That's was also my question/answer ;-)

    Please verify my answer, thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans