Resolved Issues in 37.017.00.00 and later
Not all resolved issues are included on the page below when the release notes are first published. This page will be continuously updated bi-weekly for the subsequent sandbox releases until the next quarterly release.
Issues resolved in 37.017.00.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-35621 | Reporting | An issue with the Accounting Report | The execution of the Accounting Report resulted in an error because the MJE period and MJE reversal period used for filtration were added to the report's layout. This issue is now fixed by making the MJE period and MJE reversal period filter-only columns. | |
ZR-35665 | CPD |
CPD displays Incorrect data for Data Readiness Exception |
Data variance between Reporting and CPD was observed due to the exclusion of extinct revenue contracts only from the Waterfall report and not from other reports like RC Rollforward. This issue is now fixed by removing the previously applied condition to exclude extinct revenue contracts. | |
ZR-24034 | 420131 | Reporting | An issue with the Audit Trail report generating multiple lines | The Audit Trail report generated multiple entries when a role privilege was modified. This issue was due to missing information and the dependent privileges of the parent privilege being changed. This issue is now fixed by incorporating the following information into the Audit Trail report.
|
Issues resolved in 37.017.01.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-35562 | 469225 | LT/ST | Unavailability of LT/ST schedules and summaries | The system did not generate LT/ST schedules and summaries for Revenue Contacts without current period schedules. This issue is now resolved. |
ZR-34828 | 469930 | Revenue Release | Over recognized revenue |
The system recorded more than 100% of the revenue when a decrease in price was collected for the same period prospective. The system could not process the deferral because the line start date was a future date. This issue is now fixed by configuring the system to accurately defer and release the lines.
|
ZR-36406/ZR-35751 | 476670/469754 | Zuora Revenue Login | An issue with the login | Network latency caused login sessions to expire and redirected you to the login page again. This issue is now fixed. |
ZR-34814 | Data Collection | The system infinitely generates CM-C |
When a sales order line is in a deferred state and CM/CM-R is configured with a fixed credit rule or the CM Def knock-off profile is configured to N, the system will reduce the allocatable, but the CM remains in a deferred state until the line is released to knock off the revenue. The Billed Def amount will be available even though the allocatable is reduced.
Using these validations, the system will stop the line from staging with the CREDIT MEMO CANNOT BE REFERENCED TO EXISTING LINES error message. |
Issues resolved in 37.017.01.01
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-36832 | Data Collection | An issue with staging | When a line in Zuora Revenue contains CM/CM-R and original SO line ID is a null original invoice line ID, the system stops the line in staging with “CREDIT MEMO CANNOT BE REFERENCED TO EXISTING LINES“ error. This issue is now fixed by introducing a new profile called ALLOW_CREDIT_MEMOS_POINTING_ORDER_OR_INVOICE which will allow the collection of CM/CM-R referencing to SO/INV in Zuora Billing. |
Issues resolved in 37.017.02.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-36407 | Data Collection | Performance issue with Data Collection | A technical issue caused the Data Collection job to run long. This issue is now fixed by making code changes. | |
ZR-34867 | 462178 | Allocation | Incorrect allocation revenue schedules after Type 4 | When an impairment type line is partially released, and the POB is non-distinct, the unscheduled adjustment amount does not populate accurately, resulting in incorrect allocation revenue schedules. |
Issues resolved in 37.017.03.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-36609 | 471886 | Security and Access | Unable to import roles from Zuora Revenue’s sandbox environment | Due to configuration issues, importing roles from Zuora Revenue’s sandbox environment was not working. This issue is now fixed by configuring the Sandbox environment appropriately. |
ZR-36421 | Reports | RC Rollward Report displayed operators in the amount filter | The RC Rollward Report displayed contains and does not contain operators in the amount filter. These operators are now removed. |
Issues resolved in 37.017.04.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-36984 | 481215 | Allocation | An issue with manually reverting SSP | When you manually reverted an SSP, the system did not revert the manual FV flag and the SSP group id. This issue is now fixed. |
ZR-35861 | CPD | An issue with Variance drill-down page | The Variance drill-down page of the Accounting Analysis tab displayed unbilled revenue contracts as ‘Report Summarization Variance.’ This issue is now fixed. | |
ZR-38292 | Allocation | An issue with the released allocation |
Issues resolved in 37.017.05.00
Engineering tracking ID | Support tracking ID | Impacted functionality | Reported Issue | Resolved Issue |
ZR-36805 | Reports | Revenue from Prior Period CA CL Report has blank company code | When a revenue contract is manually created, the Revenue from Prior Period CA CL report displays blank code. This issue is now fixed. |
Issues resolved in 37.016.00.00
See Resolved Issues in 37.016.00.00 and Later to get a complete list of all issues resolved in this release.