You need to sign in to do that
Don't have an account?

Opportunity Line Item Quantity is Truncated - But Only Thru SF GUI
I have professional services line items that I add through the SOAP API and through the data loader and these external tools allow me to add values such as ".385" days. When I try to add the same value through the SF GUI it truncates the value to ".38".
This is frustrating since the database obviously allows long decimals.
Has anyone found a way to allow the user to add quantity values with more than 2 decimals for opportunity line items, or any other numeric field with this limitation? I'm wary of creating my own quantity field as this is will inevitably foul up some other reports we've already written.
Does anyone have a workaround? I have already tried creating a trigger that updates the quantity based on a custom field, but the field is always truncated.
I hope there's an easier solution than creating a custom field and sending an outbound message to update the field with a web service, but I don't see any other way to solve this.
Thanks
Message Edited by prb on 11-25-2008 07:04 AM
This is frustrating since the database obviously allows long decimals.
Has anyone found a way to allow the user to add quantity values with more than 2 decimals for opportunity line items, or any other numeric field with this limitation? I'm wary of creating my own quantity field as this is will inevitably foul up some other reports we've already written.
Does anyone have a workaround? I have already tried creating a trigger that updates the quantity based on a custom field, but the field is always truncated.
I hope there's an easier solution than creating a custom field and sending an outbound message to update the field with a web service, but I don't see any other way to solve this.
Thanks
Message Edited by prb on 11-25-2008 07:04 AM
Also, you said:
Did you try your "alternate" field as a number field, instead of currency, with 3 decimal places then updating the ListPrice with your trigger?
APEX has the same behavior as the GUI. It truncates the decimal when you update or insert.
Only the data-loader and the API allow you to post a 3-digit value.
I suspect because they are parsing the String value into a Double value in the SOAP API.