Increase Included Units limit in Product Charges

[pnedyalkov]

Right now, Zuora Quotes allows for up to 9-digit Included Units to be specified for Overage type charges when configuring a product in a Quote. This means up to 999,999,999.

It will be much better, and it's needed, to allow at least up to 12-digit numbers to be used. We have clients that consume billions of units per month, so the only way to quote them is to manually change the Word/PDF file generated and then upon sending to Z-billing running a one-time amendment increasing the Included Units to the correct limit.

Zuora itself allows this, but Zuora's Quotes application for SFDC is not consistent.

When will this be implemented?

[mpersaud]

I have a case in for this issue, and they suggested a custom filed, which does not make sense when there is a standard filed with length 9. We just upgraded Zuora_Quotes and 360 to the latest version from 6.54 and 2.110. This is an issue in 6.54 and 9.1, when the limit for filed in set or 9. We will have Zuora be the primary for catalog maintenance and synced to Salesforce, the issue we face now is object ProductRatePlanCharge include field zqu__IncludedUnits__c,  the catalog sync failed because one of our charge included units is 1.2B Pixels (1200000000) and cannot update Salesforce. The reason why this was not an issue before is the rate  plan with this charge was never used and could have thrown an error on Quote if it was sold. Please review and let us know if this can be considered to be implemented.

[mliang]

We recently have ran into a similar issue in creating a quote through Zuora CPQ in Salesforce. Product rate plans with usage over 1 billion fail to get added in the quoting process. We receive error:

zChargeGroupActions.applyNewProductAmendments) Insert failed. First exception on row 0; first error: NUMBER_OUTSIDE_VALID_RANGE, Included Units: value outside of valid range on numeric field: 2250000000.00000: [zqu__IncludedUnits__c]ystem.DmlException:Insert failed. First exception on row 0; first error: NUMBER_OUTSIDE_VALID_RANGE, Included Units: value outside of valid range on numeric field: 2250000000.00000: [zqu__IncludedUnits__c]zqu)

Zuora has reproduced error on their end, but can anyone provide a workaround or temporary solution? Also, when will this be resolved?

Thanks

[nathanc]

Hi this one is a little hard for us to change.  Right now we have it at 9 decimal places (which Zuora also allows) which then limits you to 9 digits (since Salesforce only lets you define 18 for custom fields. 

In any case, we could reduce the decimal places and increase the whole numbers, but then we have to be absoblutely sure we do not have any customers, ever, that need to do usage to 6,7,8,9 decimal places.  

So we have to go through this analysis before we can make a change like this, or we block another set of customers.  Would be great to have feedback from the community if we have, know of or have seen use cases for usage taking us beyond 5 decimal places.

[mpersaud]

Hi Nathan,

Can you confirm if this is resolved with Zuor Quote 9.11, we just upgraded and don't see this error anymore.

Thanks,

Marvin