Could not save view error when trying to modify a view in Modern UX.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

In MUX, if the original view is deleted and then a new view is created with the same name, this causes an issue with view target id for any UNSAVED views and leads to error "Could not save view" in MUX and ODF-0015: Value must be unique in app-ca logs.

 

STEPS TO REPRODUCE:
1. Login to Clarity As Administrator. Navigate to Modern UX.
2. Navigate to Staffing Plan -> Allocations by Resource.
3. Modify few columns on the grid and save the view as "Test View". Open The views drop-down -> Manage and share the view with everyone.
4. Copy the link of the view.
5. Navigate to Blueprints -> Pages and make a copy of the Standard Page Blueprint. Edit the blueprint and add a channel. Paste the link of the view copied into Channel URL and add &puiFullscreen=on&puiHidePPMTabs=on
6. Publish the Blueprint. Create a Page instance and attach this blueprint to this instance.
7. Login with another user with permissions to see this Staffing page
8. Navigate to Pages -> Page instance from 6. Click on the channel. We notice the Allocation by Resource tab open up with the "Test View" view.
9. Add a new column. We will notice that the view changes to (Copy) Test View. Logout.
10. login back as Admin user, navigate to Staffing -> Allocation By Resource and delete the "Test View" view. It will revert to Standard View.
11. Make changes to the standard view and save it back as "Test View". Open The views drop-down -> Manage and share the view with everyone.
12. Copy the link of the view and edit the channel URL of the page and set it to the new URL.
13. Login back as restricted user, Navigate to Page instance with the channel and click on the Channel. 
14. We notice the Allocation by Resource tab open with "Test View" view.
15. Try modifying any columns or adding any filters

Expected Results :- View is modified with the changes.
Actual Results :- UI throws an error "Could not save view".

Note: the page does not have to have a channel to reproduce this issue, this describes one scenario that leads to the issue. 

Environment

Clarity PPM 16.2.x, 16.3.0, 16.3.1

Cause

Caused by DE154830

Resolution

Fixed in Clarity 16.3.2 and 16.3.1.1 (16.3.1 Patch 1)