Skip to main content

Resolved Issues in 37.016.00.00 and later

Zuora

Resolved Issues in 37.016.00.00 and later

Resolved issues in 37.016.00.00

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.016.00.00

Engineering tracking ID Support tracking ID     Impacted functionality Reported Issue   Resolved Issue
ZR-30322 457330 UI Issue with Real-time summarization The Real-time Summarization profile flag was undefined in the UI, resulting in the Real-time summarization not working. This issue is now fixed by configuring the Real-time Summarization profile flag to true when it is not defined.
ZR-32756 454927 UI Unable to delink RC The current restriction of selecting 126 rows from the table to link and delink resulted in not being able to delink the RC. This issue is now fixed in the table to link and delink.
ZR-31025   UI Mismatched column names and misaligned column values in the exported CSV file are now fixed.

Earlier, exporting journal entries from the Journals and Journal ID pages caused the following issues. 

  1. The column names weren’t exported in the same format as in the UI. For example, if the column name is “Account Code”, the exported version would read “accountCode” in the CSV file. 

  2. Values with a period in the exported CSV file were separated in two columns instead of appearing as a single value in one column.

ZR-30992   UI Journals and Journals ID pages now get a clean display of numerical entries. Earlier, when you have entries with long numerical values ranging up to 7 digits on the Journals and Journals ID pages, the numbers appeared in a wrapped fashion. With optimized column widths, this issue has now been fixed for a proper display of the values.
ZR-34048 456945 Data Collection An issue in scheduling job An issue in scheduling jobs occurred because the Events and Transfer accounting jobs were triggered simultaneously. This issue is now fixed.
ZR-34290   MJE Missing column in RevenueContractMJEntriesFacts objects The missing column in RevenueContractMJEntriesFacts objects occurred due to a gap in the object missing the RevenueJournalLineID column on the RevenueContractMJEntriesFacts object. This issue is fixed by adding the missing columns to enable proper joins between the other objects.
ZR-29509 443601 CPD Variances in the Close Process Dashboard

Variances in the Close Process Dashboard were a result of variance that occurred due to the LT/ST MJEs. This issue is fixed by eliminating the LT/ST MJEs in the Close Process Dashboard to match the schedules.

Issues resolved in 37.016.01.00

Engineering tracking ID Support tracking ID     Impacted functionality Reported Issue   Resolved Issue

ZR-32832

455230 UI Issue with the Revenue Summary tab The Revenue Summary tab displayed a No Data message due to the delay in the API response, and the UI did not show a message about the data loading. This issue is now fixed by adding a Data Loading message on the UI of the Revenue Summary tab.
ZR-34388 456351 UI  An issue in viewing DYN labels

The issue with viewing DYN labels in the UI is now fixed by making code changes. 

ZR-34666   Reporting An issue with viewing the Waterfall report There was an issue with viewing the Waterfall report due to an error in mapping the header and data fields. This issue is now fixed.
ZR-34611   System  An issue with resetting the API password

The issue with resetting the API password is now fixed by making code changes. 

ZR-34436   CPD/Data Collection An issue with CPD and Data Collection jobs Unprocessed data was reported due to jobs of the Close Process Dashboard triggering along with the Data Collection job. This issue is now fixed by configuring the  CPD jobs to begin only after the Data Collection jobs are complete.
ZR-27387 432668 CPD/Reporting Variances in CPD and Rollforward report Variances in the Close Process Dashboard and Rollforward report were a result of a change in the schedule type condition. This issue is now resolved by making conditional changes to the schedule type.