function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion


Hi All,

We are facing a strange error while saving a record.
We have multicurrecy enable for our org and on opportunity we have a field "Net Value" which is a curreny field (18,0) and we have written a custom lightning component to create/edit a opportunity, we do not use classic anymore.
Issue which we are seeing are coming only for european countries but not on all opportunity records.

On some records when user which is also the owner of opportunity tries to save opportunity they get NUMBER_OUTSIDE_VALID_RANGE error on "Net Value" field but we do not have any code written which change field value. But when same record is been saved by Admin who is not the owner of opportunity then error do not comes and goes away permanently. 

We are not able to understand why Lightning behaving like this, Did anyone come across any error like this.

Thanks in Advance,
Banwari KevatBanwari Kevat
Hi puneet,
   Can you please check the locale of users. Currency format is changed based on locale. Some EU countries have differennt currency format. 
Please use comma as decimal notation instead of dot.
  Please share your code and both users detail with locale and currency .
I'll see.

Banwari KevatBanwari Kevat
Below is the same error.
User-added image

You can see here that if i am using dot as . then its giving me error.
Deepali KulshresthaDeepali Kulshrestha
Hi Puneet,
Please refer to the links provided below:
I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.

Thanks and Regards,
Deepali Kulshrestha

Thank you both for the reply, I know its a year late reply and I am sorry for it.

The issue was with Oracle CPQ package and Salesforce, integration from Oracle was behaving very stranging and updating the salesforce value irrespective of the range and somehow was able to commit it as well and it was happening only for European countries.
We haven't received any help any of the side and we end up writing our custom logic in before insert/update to correct the data.