Release notes
2026.7.2
July 2026
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.
What's new
To learn about the new features or enhancements in this release, please see the What’s New page.
Resolved issues
Note that the current build is always cumulative: it contains all previous patches.
| Released | Ticket | Area | Description |
|---|---|---|---|
| July | 189199 | Template Studio | Column widths in Template Studio did not adjust correctly. |
| 198963 | Workflow | An apostrophe in a workflow task name caused a SQL syntax error during data refresh. | |
| 201174 | Dashboards | A filter error prevented dashboards from displaying correctly. | |
| 203073 | Mapping Table | The mapping table for blank members did not work correctly in Drill Across. | |
| 204178 | Publish Process | ProCalc formulas using Sum and Max failed to publish. | |
| 208588 | Template Studio | Filters in templates did not update according to the settings defined in Security Manager. | |
| 214155 | Data did not commit when a member key value was set to N/A | ||
| 216052, 215928, 220148 | Processes | Data precision settings did not save when users clicked Save | |
| 216261, 216939 | Detailed Planning Manager | Duplicated scenarios in the DPM did not reflect changes made to attributes or employees. | |
| 217139, 215363 | Ad Hoc Analysis | Ad Hoc Analysis performed slowly. | |
| 217518 | List attributes had an incorrect character limit. | ||
| 217947 | Template Chart Editor | The Legend Position drop-down in the Template Chart Editor had no available options. | |
| 217956, 221619 | Template Studio | Leading zeros in member keys were not retained in templates compared to data views. | |
| 218887 | Ad Hoc Analysis | The Rule set page displayed incorrectly. | |
| 219215 | Journals Manager | Users were unable to duplicate a journal entry. | |
| 219223 | Template Studio | Templates produced an error when the region or language setting was changed. | |
| 219570, 215803, 218849, 221038, 221476 | Processes | An edited scheduled process did not run at its new scheduled time. | |
| 219865 | Model Manager | Adding a new member in Model Manager caused an error when the language was set to POL. | |
| 220072 | The Import process ran without completing. | ||
| 221333 | Detailed Planning Object | A character limit caused duplicate members in the list attribute type. | |
| 207704 | Detailed Planning Manager | Duplicate keys caused a DPM import to report success while importing zero records. | |
| 220948 | Template Studio | An image or logo appeared distorted in Report mode. | |
| 218406, 219225 | Model Manager | Numeric custom member properties in reports omitted commas when the German region setting was used. | |
| 219243, 220897, 220894, 222290, 222469 | Ad Hoc Analysis | Year-to-date drill-across did not work. | |
| 218396, 219101 | Security Manager | The Security Audit Report failed to export when a non-English region setting was used. | |
| 221083 | Summary Posting Report | Journal entries with an Unposted or Unposted and Deleted status appeared as Posted in Summary posting reports. | |
| 216624 | Detailed Planning Manager | Schedules could not be edited, and attributes other than text could not be viewed or selected. | |
| 218111 | Template Studio | Page Hierarchy Groups using the [All] member returned a “no access to any pages” message on View > Preview, and Auto Generate failed to group data views with an [All] member key. | |
| 221670 & 221776, 221743, 221824, 222219 | Model Manager | A data view did not display values for time periods outside a version's configured date range. | |
| 220732 | InfoFlex Process | An OLAP InfoFlex run on PostgreSQL failed with a “relation does not exist” error caused by a temp-table name casing mismatch in the delete-data-from-source path; a related SQL query also timed out separately. |
Known issues
| Area | Description | Workaround |
|---|---|---|
| Process Manager | Executing a Refresh Process after a Remove Data process writes nulls as zeros. | Run a Publish after any Remove Data process to commit nulls correctly. |