R 25 - June 2024

Feature Enhancements

A new notification added to show the percentage progress of the data updates running on a calculation that is being opened.
This notification also updates the user with a success message when the data updates are completed.
The calculation open routine does not timeout during the data updates, hence, does not throw any errors or red banner messages.

Line items functionality is now enhanced to support sharing of the line items across the clients (applicable to Client Manager enabled database accounts).
Users can select the line items of their choice and mark those to be made available across the clients in a database.
“All clients” checkbox provides users a convenience to mark all the line items in one go. These line items are formatted in bold on the “Insert Line Item” screen to differentiate these from other line items (which are local to the current client).

Entities can be reordered or reparented within the group easily with drag/drop controls now.
When users mouse hover on an entity, there are two types of icons displayed.
When it shows double vertical arrow icon, it allows reordering of the entities within/across the groups.
When it shows the hand icon, it allows reparenting of the entities within/across the groups.

Fetch print configuration for a calculation (e.g., print styles, applicable sheets to print etc.)
Initiate print on one or more calculations.
Get status of a print job.
Download print PDF.

Return all datasets (showDatasets=all).
Return only active datasets (showDatasets=active). This is also the default option.
Return only deleted datasets (showDatasets=deleted).
Indicate with a new parameter in the response (deleted=true/false) whether a dataset is a deleted dataset or an active one.
Allow searching for a dataset with its name (dsName=”My 2023 Dataset”).

Consolidated status of the operations (e.g., it responds with a Fail status if at least one of the operations initiated on a dataset is failed).
Status of individual operations such as:
Create Dataset
Edit Dataset to
Rename a dataset
Change it’s purpose
Add and remove entities
Delete calculations

Date filter –
This is optional, when absent, it looks for the data from last 6 months which is maximum period. Date filter can be included to get fewer records.
User filter –
This is optional, when absent, it brings the data without filtering the records based on who initiated these dataset operations. User filter can be included to fetch only the records for the operations initiated by specific user.

Fetch the insertable sheets according to the template the calculation is created from.
Insert one or more sheets into a calculation.

Enhanced the performance of inserting the sheets into calculation. This will especially benefit large calculations with many sheets.
Enhanced the performance of sort (Tools>Sort) functionality. This will especially benefit the large Group/Consol calculations.

Notable Defects Remediated

User added selector formulae (DROPDOWN() or SELECTTICK()) were not editable, couldn’t be deleted. Reset to system cell was the only option to remove these formulae.
Decimal format applied (Format>Cells>Decimal Places) was not effective until a refresh.
Copying a date from one cell and pasting it in another cell that expects a date was resulting in a “Must be date” error.
Inserting analysis sheets for columns was failing especially on wide sheets with many columns.
Calculation upgrade was not bringing the page breaks defined in the new version template on to the upgraded calculation.
Template selection for the newly added entities in a dataset during roll forward / copy was not being respected, because of this the calculations were being created against undesired templates.
There was an intermittent issue where deleting calculation for an entity in a dataset was not working.
Fixed a few cases which were causing the workbook service to crash. This was impacting the opening of the calculations.

There was an issue where deleting an associated journal does not delete the data from a few sheets in a calculation.
There was an issue where the drilldown does not work on the imported data brought through code based imports if both code based and target based imports were run on the same calculation.
There was another issue where deleting a journal associated to code based import also deletes the data imported through target based import if both code based and target based imports were run on the same calculation.
Re-running an existing import job was stuck in “Pending” state if the entity the import was run for has been renamed in the Entity Manager. Re-run job correctly picks up the updated entity name and updates the status.
Round to whole amounts
functionality during the import was not working. Irrespective of the value given to this setting, the import was always rounding the amounts to whole numbers.

Print job initiated with a print style which has a trailing space in its name was failing.
Print was failing when printed using a print style with logos configured and marked as “All clients” if attempted from a client where the style was not originally created in. It was only working in the client where it was created.

There was an issue where the Edit Dataset API was not responding with an error message when a duplicate dataset name supplied to it. It incorrectly treated the name as not a duplicate because it was doing a case sensitive comparison on the names.
There was an issue where Edit Dataset API was not allowing to add entities and associated calculations using client templates, this is working only with standard templates.

Issues to be remediated in a future release

Copy the dataset which has the client template to the next year. The client template will still be associated with the same year/version template after this step.
Upgrade the client template to the next year template.
Do necessary changes to the client template and save it.

Disabled sorting / filtering on the following column(s) is impacting the performance.
Return
Submitted Time
Disabled Filter by Condition on the following column(s) is impacting the performance. Sort, Filter by Value work on these columns.
Amended Return
Status
Jurisdiction
Source
Filtering does not work on the following column(s). Sorting still works.
Submitted Date/Time
Queued Date