openerp-india team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello,

This issue has already fixed in latest trunk version with using a "Payment Term" 's decimal accuracy for value_amount field.
Such as  'value_amount': fields.float('Amount To Pay', digits_compute=dp.get_precision('Payment Term'), help="For percent enter a ratio between 0-1.")

Which will available soon for the next version.

So this issue only affect for the stable version but this is not a blocking point that's why we can not consider this issue as a fixes for stable version.
For these type of issues If you have a support and maintenance contract with us then you can contact our OPW team at support@xxxxxxxxxxx.

Thanks.


** Changed in: openobject-addons
       Status: New => Won't Fix

** Summary changed:

- value_amount in account.py doesn't specify precision
+ [v6]value_amount in account.py doesn't specify precision

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/882564

Title:
  [v6]value_amount in account.py doesn't specify precision

Status in OpenERP Addons (modules):
  Won't Fix

Bug description:
  value_amount doesn't specify precision, so it ends up using only 2
  digitis precision. This is too little so we can't specify 2,5% for
  example.

  Is this going to be fixed for openerp 6.0 or should we just fork it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/882564/+subscriptions