Release notes

2024.1.0

March 2024

Release notes describe the enhancements and bug fixes contained in new releases and maintenance releases.

 Tip: To find the release note that contains a specific issue, search on the Prophix Support Desk ticket number.

Support for Microsoft 365

Analyzer and Contributor support Microsoft 365 using monthly or Semi Annual Channels.

 Note: Microsoft Office 2019 and Office 2016 perpetual licensed editions are not supported.

What's new

Release 2024.1.0 consists exclusively of resolved issues.

Resolved issues

Note that the current build is always cumulative: it contains all previous patches.

Released	Ticket number	Area	Description
March	163059	Advisor	A data collection issue caused Advisor to fail. (Advisor build 2023.1.2.)
March	165893, 166463, 160451, 159529	Advisor	The Advisor Report Generator lambda failed to generate reports. (Advisor build 2023.1.2.)
February	133258, 135585, 141324	Analyzer	If the view contained more than 8,000 rows, the connection to Excel was lost.
February	142712, 141717, 148019, 161944	Contributor	If the view contained more than 8,000 rows, the connection to Excel was lost.
February	164029	Model Manager	In Procedural Calculations, the auto recalculate in data entry function was not available even when a simple formula was entered.
February	160755	Process Manager	The Process Execution Service crashed repeatedly.
February	160645	Process Manager	The Update Cube process (with the Process full option) and the Publish process failed to merge records into the fact table
February	163156	Process Manager	Using the InfoFlex process to create a new version, the process returned the error Attempt to copy cell comments failed.
February	164786, 165265	Process Manager	In the InfoFlex process, if the Target Members tab contained an MDX-based member property named set, selecting the Dimension Spread tab caused an error.
February	162606, 160421	Templates	Entering Row Notes and then clicking  (Refresh) returned the error: The wait operation timed out.

Known issues

Area	Description	Workaround
Audit Log	Adding a True/False custom member property to a dimension causes Audit Log to add a record for every member in the dimension, as if the members had been edited.	An upcoming release will address this issue.
Detailed Planning Manager	In Detailed Planning Attributes, after you duplicate an attribute and then proceed to rename the duplicate, if at any point in the editing process the new name matches the old name, in any calculations that use the original attribute, DPM immediately replaces it with the duplicate attribute. For example, you select the attribute Asset Class and click the Duplicate option, creating Copy of Asset Class. Then, to give the attribute a unique name, you start by selecting Copy of and deleting it, intending to make the name unique by adding 2, to create Asset Class 2. However, the moment Copy of Asset Class becomes Asset Class (and though you have not Saved) in every calculation that uses Asset Class DPM replaces the existing one with the duplicate.	To prevent DPM from swapping the duplicate for the original attribute, do either of the following when renaming: Add the unique part of the new name before you remove the prefix. That is, first change Copy of Asset Class to Copy of Asset Class 2, then delete Copy of. Select and delete Copy of Asset Class, then type a name that at no point matches the old name.
Detailed Planning Schedules	When adding a new object/employee by populating the fields of the Add Employee Member dialog, upon returning to the schedule red borders appear around some cells and remain until the schedule is saved.	No workaround is necessary. This is a cosmetic bug only. An upcoming release will address this issue.

Area

Description

Workaround

Audit Log

Adding a True/False custom member property to a dimension causes Audit Log to add a record for every member in the dimension, as if the members had been edited.

An upcoming release will address this issue.

Detailed Planning Manager

In Detailed Planning Attributes, after you duplicate an attribute and then proceed to rename the duplicate, if at any point in the editing process the new name matches the old name, in any calculations that use the original attribute, DPM immediately replaces it with the duplicate attribute.

For example, you select the attribute Asset Class and click the Duplicate option, creating Copy of Asset Class. Then, to give the attribute a unique name, you start by selecting Copy of and deleting it, intending to make the name unique by adding 2, to create Asset Class 2. However, the moment Copy of Asset Class becomes Asset Class (and though you have not Saved) in every calculation that uses Asset Class DPM replaces the existing one with the duplicate.

To prevent DPM from swapping the duplicate for the original attribute, do either of the following when renaming:

Add the unique part of the new name before you remove the prefix. That is, first change Copy of Asset Class to Copy of Asset Class 2, then delete Copy of.
Select and delete Copy of Asset Class, then type a name that at no point matches the old name.

Detailed Planning Schedules

When adding a new object/employee by populating the fields of the Add Employee Member dialog, upon returning to the schedule red borders appear around some cells and remain until the schedule is saved.

No workaround is necessary. This is a cosmetic bug only. An upcoming release will address this issue.