In the Modern User Experience Per Period Metrics (Time Scale Value (TSV)), error: An Exception occurred while trying to update an object instance assignment is generated when the Time Slicing job is run and updates are made to Per Period Metrics at the same time. This error can happen if updating cells one by one, copying and pasting data, or clicking refresh using Group By. When the error happens, some of the data entered is reverted back to the previously set value. This is more noticeable if the time slicing job takes 30 seconds or more to process.
STEPS TO REPRODUCE:
Expected Results: Refresh completes successfully and data changes are saved post refresh
Actual Results: Intermittently, a Toast error message: An Exception occurred while trying to update an object is generated. Additionally, some of the data reverts back to the previous values.
Note: This issue also happens while copying and pasting data into per period metrics cells and also trying data cell by cell.
This is caused by: DE61044 related to a deadlock issue when the time slicing job and per period metrics are being updated at the same time. Excerpt of error seen in app-ca.logs:
ERROR 2021-05-21 09:31:55,509 [http-nio-1577-exec-456] rest.validation (clarity:admin:..::PPM_REST_API) com.niku.union.odf.exception.ODFServiceException: An exception occurred while trying to update an object instance assignment
Caused by: com.niku.union.persistence.PersistenceDeadlockException: SQL error code: 1205Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Release : 15.9.2
Component : CLARITY PROJECT MANAGEMENT
Database: MSSQL Server
This issue is fixed in 15.9.2 patch 1 and 15.9.3 as DE61044
Workaround: Schedule the Time Slicing job to run less frequently to help avoid the issue.