Announcements
The "Actual value" on "Opportunity Closed" entity had a negative value in Version 1710 (9.1.0.4632) online
But in Version 1710 (9.1.0.5220) online, negative values not allowed, anyone else experiencing this?
*This post is locked for comments
Hi
I have tested on my trial and it allows to enter negative values, please see below
If anything, it could have been caused by the 5220 updates possibly.
Try to update it through dynamic excel sheet ,it will allow you to update the negative value on actual revenue & also the opportunity will be closed.
Hi,
Any update on this issue ? Even i am facing this problem.
The "Actual Revenue" on "Opportunity Closed" entity use to accept negative value in versions before 1710 (9.1.0.5220) online.
But after Version 1710 (9.1.0.5220) online, negative values are not allowed in this field. My CRM version is 1710 (9.1.0.5222) online.
I am getting below error message while closing any opportunity with negative actual revenue.
"message":"A validation error occurred. The value of 'actualrevenue' on record of type 'opportunityclose' is outside the valid range."
Thanks,
Ravi
Ravi, Try to close the opportunity through excel-->means through excel update the actual revenue with negative value &status as won. You will not receive the error.
Hi Amit,
Yes, i can do it through excel but it is a workaround and not a solution.
Ideally, we should be able to close an opportunity via CRM interface and not through excel.
Hi guys. I experienced the same issue. I am using version 1710 (9.1.0.5228). Is this caused by Microsoft?
Upon checking, Minimum Value was set to 0.0000 which supposed to be set to the lowest negative value.
I even check it to a trial environment. By default, negative value should be the Minimum Value.
Do you guys have any updates regarding this issue?
Folks,
I have raised a ticket with Microsoft.
As per MS, this issue is a bug and seems to be fixed in the 9.2 update.
As of now I have got this issue fixed for my CRM instance by asking MS to on demand run the mitigation script only for my instance.
I see the same issue in some of our environments. Comparing three environments and their version numbers, I observe the following for the value of actualrevenue on opportunityclose:
Environment 1, 9.1.0.5426: Minimum value: -922.337.203.685.477,0000
Environment 2, 9.1.0.5426: Minimum value: -922.337.203.685.477,0000
Environment 3, 9.1.0.5426: Minimum value: 0.0000
This would thus not appear to be directly tied to the version number, but it sounds good that a fix is underway.
I had hoped I would be able to fix this myself by changing the minimum value directly, or by importing a solution containing the correct minimum value for actualrevenue. Unfortunately, neither of these approaches turned out to make any difference.
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.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
