As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Raising this issue again. There is a github issue logged for the matter here also: https://github.com/frappe/erpnext/issues/1475
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
On Friday, August 29, 2014 7:08:56 PM UTC-7, Federico Torreti wrote:
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Our new feature "Fieldwise precision setting" will address this. Right?
On Sat, Aug 30, 2014 at 7:38 AM, Federico Torreti <to...@gmail.com> wrote:
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Our new feature "Fieldwise precision setting" will address this. Right?
On Sat, Aug 30, 2014 at 7:38 AM, Federico Torreti <to...@gmail.com> wrote:
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
On Friday, 5 September 2014 06:23:54 UTC+8, Jev Björsell wrote:
I would welcome this approach greatly.
On Friday, August 29, 2014 7:08:56 PM UTC-7, Federico Torreti wrote:
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
I had a chat with the team regarding this. We have fixed losses due to fractions in most places. If you come across an instance where you have experienced a loss due to fraction, please post it.
If there is some place we cannot fix it, then we can introduce a quantity multiplier in Item Price - but I am not sure how deep we will need to take this (seems like a open ended project right now)
On 15-Sep-2014, at 3:03 pm, Federico Torreti <to...@gmail.com> wrote:
Hi Rushabh - Any thoughts on this proposal?
On Friday, 5 September 2014 06:23:54 UTC+8, Jev Björsell wrote:
I would welcome this approach greatly.
On Friday, August 29, 2014 7:08:56 PM UTC-7, Federico Torreti wrote:
Rushabh - Folks a proposal to resolve the issue of decimals, floats and currency would be to use a unit price multiplier in the item master as several ERP system do regarding currency type with only 2 decimals, while doing calculations with whathever float arithmetic precision the user sets up in the global settings. For example let's say my unitary price before tax is: 3.223324 (yes unfortunately it can be that long) all I had to do in the past when using a different system was to set a multiplier to 10000, 6 digits for float calculations and the unit price would be recorded as: 32,233.24 in a currency field.
Any rendering of the price in any reports would be currrency field value/multiplier and therefore displayed as 3.223324.
We are having a hard time with the changes to data types because due to the large number of vendors, and constantly changing rates, we often have the need to work with 5 or 6 digits.
Having changed all the field types to Float, you can imagine what that does to all our reports, invoices, quotations...
What is your idea about implementing a multiplier and leave all currency fields as such?
On Friday, 11 July 2014 10:00:56 UTC+8, Rushabh Mehta wrote:
Jev, we will discuss this today and let you know when we can schedule this.
On 11-Jul-2014, at 12:43 am, Jev Björsell <eb...@gmail.com> wrote:
Hi Guys,
Sorry to be the broken record, any updates on this matter? Will if be addressed, or is precision greater than 2 decimals on unit price a 'Wont Fix' matter?
Thanks
-Jev
On Wednesday, June 25, 2014 5:56:13 PM UTC-7, Jev Björsell wrote:
Can the precision matter for rate be addressed now that 4.0 has been shipped?
Thanks,
-Jev
On Monday, March 10, 2014 3:45:57 AM UTC-7, Umair Sayyed wrote:
Hello Jev,
Fields in question Price List Rate, Basic Rate and Amount are "Currency" Field. If you want value of Float Precision to have impact on these field, you will need to change their Field Type from "Currency" to "Float".
You can change field type of a field from Customize Form.
On Sun, Mar 9, 2014 at 4:01 AM, Jev Björsell <eb...@gmail.com> wrote:
The same is true for the import rate fields on Purchase Invoice Items.
On Saturday, March 8, 2014 2:30:01 PM UTC-8, Jev Björsell wrote:
As the subject says, my system has Float Precision set to 4, but when creating a PO, the Line Item unit price always rounds to two decimal places. There appears to be java script code that is forcing the rounding.
I'm running v3.8.9.
This issue is really hurting us, some quick help would be greatly appreciated.
Thank you,
-Jev
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Hi Rushabh - I tried working with your new “float precision” functionality.
We still have problems as the decimals is limited to 6 and there is no way to set-up purchasing item price inclusive of VAT which is not the case for Sales price.
It happens that if a negotiated price for example is USD 2.60 with a VAT of 17% you would have a Item Price Rate of 2.222222223. The issue is that in some cases price is negotiated net of VAT in some cases not.
I think a way to fix this without messing around with item price rate and multipliers may be to have the ability to have the option to fix the item rate inclusive or not of VAT as we do for sales.
Float idea could be a workaround until 5.1 but to make it usable would need to have at least 9 digits from the max of 6 currently available. If not, I will think about how to play with discounts or manually adjust the VAT rate.