Hierarchy Status Module: Views on the Status module page do not save correctly and gives error message
Article ID: 231079
Updated On:
Products
Issue/Introduction
Hierarchy Status Module: Views on the Status module page do not save correctly and gives error message.
Steps to reproduce:
Hierarchy Status Module: Save a new view, add Status Report object fields, then move columns in the order desired, save view. Refresh page, system gives error toaster message and column order reverts to original (order before you arranged columns and saved view).
Steps to reproduce:
- Go to Hierarchies
- Create a hierarchy and add investments with Status Reports (e.g. projects with status reports)
- be sure to create a custom Hierarchy blueprint and add the Status module, and associate your new hierarchy
- go to Status module on your Hierarchy, you should see some status reports showing (for example a mix of draft and final reports)
- Click Columns and add several Status Report fields
- Rearrange new columns and save View
- Refresh page and system will give toaster message error on page and create an error message in the log
Expected Results: View saved and column order saved
Actual Results: View does not save correctly and column order reverts
Note: When you do save a View, the columns added save (add 10 fields and 10 fields stay when saving), but any rearranging of the columns and saving does not work. Configuration to the Details Flyout fields DOES save and field arrangement stays.
Error message in log:
SQL error code: 0
Error message: ERROR: current transaction is aborted, commands ignored until end of transaction block
Executed:
update odf_ui_views set OWNER = case when ? = 2 then OWNER else ? end, IS_SYSTEM = case when ? = 2 then IS_SYSTEM else ? end, CODE = case when ? = 2 then CODE else ? end, VIEW_MODE = case when ? = 2 then VIEW_MODE else ? end, ASSOCIATED_OBJECT_TYPE = case when ? = 2 then ASSOCIATED_OBJECT_TYPE else ? end, VIEW_CLASSIFIER = case when ? = 2 then VIEW_CLASSIFIER else ? end, TYPE = case when ? = 2 then TYPE else ? end, IS_DEFAULT = case when ? = 2 then IS_DEFAULT else ? end, VIEW_TARGET_ID = case when ? = 2 then VIEW_TARGET_ID else ? end, BLUEPRINT_ID = case when ? = 2 then BLUEPRINT_ID else ? end, ASSOCIATED_INSTANCE_ID = case when ? = 2 then ASSOCIATED_INSTANCE_ID else ? end, IS_SHARED = case when ? = 2 then IS_SHARED else ? end, NAME = case when ? = 2 then NAME else ? end, last_updated_date = ?, last_updated_by = ? where 1 = 1 and id = ?
ERROR 2021-12-09 12:11:06,942 [http-nio-8080-exec-2017] rest.validation (clarity:[email protected]:45528353__236FC220-5084-483C-8A40-D00B4B0A5F0B:PPM_REST_API) ExceptionInfo :: Could not update resource. Resource name: views. Error code: null Error message: Creating instance of: odf_ui_view
Environment
Release : 16.0.0
Component : Clarity MUX UI Usability
Cause
STEPS TO REPRODUCE:
1- Go to Hierarchies
2- Create a hierarchy and add investments with Status Reports (e.g. projects with status reports)
3- Be sure to create a custom Hierarchy blueprint and add the Status module, and associate your new hierarchy
4- Go to Status module on your Hierarchy, you should see some status reports showing (for example a mix of draft and final reports)
5- Click Columns and add several Status Report fields
6- Rearrange new columns and save View
7- Refresh page and system will give toaster message error on page and create an error message in the log
Error message in log:
SQL error code: 0
Error message: ERROR: current transaction is aborted, commands ignored until end of transaction block
Executed:
update odf_ui_views set OWNER = case when ? = 2 then OWNER else ? end, IS_SYSTEM = case when ? = 2 then IS_SYSTEM else ? end, CODE = case when ? = 2 then CODE else ? end, VIEW_MODE = case when ? = 2 then VIEW_MODE else ? end, ASSOCIATED_OBJECT_TYPE = case when ? = 2 then ASSOCIATED_OBJECT_TYPE else ? end, VIEW_CLASSIFIER = case when ? = 2 then VIEW_CLASSIFIER else ? end, TYPE = case when ? = 2 then TYPE else ? end, IS_DEFAULT = case when ? = 2 then IS_DEFAULT else ? end, VIEW_TARGET_ID = case when ? = 2 then VIEW_TARGET_ID else ? end, BLUEPRINT_ID = case when ? = 2 then BLUEPRINT_ID else ? end, ASSOCIATED_INSTANCE_ID = case when ? = 2 then ASSOCIATED_INSTANCE_ID else ? end, IS_SHARED = case when ? = 2 then IS_SHARED else ? end, NAME = case when ? = 2 then NAME else ? end, last_updated_date = ?, last_updated_by = ? where 1 = 1 and id = ?
Expected Results: View saved and column order saved
Actual Results: View does not save correctly and column order reverts
Resolution
DE63536
This is resolved in 16.0.1
Feedback
