Known Issues · Salesforce Billing
After upgrading the Salesforce Billing Package and running Post Install, an error is presented First error: [REQUEST_RUNNING_TOO_LONG] Your request was running for too long, and has been stopped. The error is observed for organizations that have huge order item records.
In Review ·Reported By 2 ·Updated 2 days ago
In Lightning Experience (LEX), CreateOrderLightning button on Opportunity and Quote objects throws an error instead of creating an Order.
In Review ·Reported By 1 ·Updated 2 days ago
An Invoice Plan can be set up such that Invoice Lines are created without a Start Date or End Date. This can lead to Revenue Recognition errors when Revenue Distribution Method depends on Invoice Line Start Date and /or Invoice Line End Date.
No Fix ·Reported By 1 ·Updated 2 days ago
When creating Usage records against a Usage Summary with existing records, a timeout is observed. The timeout occurs typically when a Usage Summary has approximately 1800+ usage records associated to it.
No Fix ·Reported By 1 ·Updated 3 days ago
Salesforce Billing lacks a validation on the Debit Note (DN) Allocation Visualforce page to prevent allocations for 0.00 and for more than the total amount of the DN line.
In Review ·Reported By 4 ·Updated 4 days ago
Use Case is one Account with several Orders to have their Invoices grouped by PO Number on one Invoice Run with two (or more) of those Orders having a duplicate PO Number with the exception that they differ by lowercase or uppercase only. The Invoice Run creates the invoices in draft with no lines,...
In Review ·Reported By 1 ·Updated 4 days ago
When Quoting subscriptions for time periods that do not include Leap Day, 366 days are being used in the denominator of the Prorate Multiplier. We should be using 365 days for these time periods. For example, set the Start Date for the Quote Line to 4/1/2019 and End Date to 10/31/2019, when calculate...
In Review ·Reported By 20 ·Updated 5 days ago
Invoices that are fully paid will sometimes show the Payment Status field = 'Partially Paid'.
Fixed in version Billing 222 ·Reported By 18 ·Updated 6 days ago
An error is returned in the debug log when using a batch job to create usage records in Salesforce Billing v218. Sample error is below: First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, DML statement cannot operate on trigger.new or trigger.old-493-
Fixed in version Billing 222 ·Reported By 4 ·Updated 6 days ago
On amendments that eventually cancel an order product, there appears to be a remainder in the Pending Billing Amount (without tax) field on the first amendment order. This appears to depend on Billing Day of Month (BDOM) changing over the amendments. BDOM changes when package setting for CPQ is Default...
No Fix in version Billing 222 ·Reported By 2 ·Updated 6 days ago
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.