Per-Period Metrics blanks out all staff / rows in 15.9.1
search cancel

Per-Period Metrics blanks out all staff / rows in 15.9.1


Article ID: 208523


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Per Period Metrics is not working / causes all rows in the grid to be removed depending on values selected in View Options. This happens for all areas where per period metrics are available including Cost Plan Detail and Project Staff. Instead of the rows displaying, a message: No Rows to Show displays.


Prerequisite: Have at least 10 years of monthly Fiscal Periods created (Example Monthly Fiscal periods from 2017-01 through 2028-01)

  1. Create a project in the Modern User Experience (UX)
  2. Go to the Staff tab and add at least one team member
  3. Click on the ‘View Options’ drop down
  4. Select 3 fields in PER-PERIOD METRICS (IE Allocation, Actuals, ETC)
  5. For Periods select Months
  6. Start Period: 2018-01
  7. End Period 2027-01

Expected Results: Rows for staff members display with the added Per Period Metrics selected

Actual Results: The Staff rows are removed and “No Rows to Show” message appears


Release : 15.9.1



This is caused by DE59834 which is due to column / row size limit. See related errors below from the app-ca.logs based on Database type:

For Oracle:

Exception reading objects: team


SQL error code: 1792

Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01792: maximum number of columns in a table or view is 1000

For SQL Server:

Exception reading objects: costplandetail


SQL error code: 1701

Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Creating or altering table 'WorkTable' failed because the minimum row size would be 14428, including 229 bytes of internal overhead. This exceeds the maximum allowable table row size of 8094 bytes.

For Postgres:

Exception reading objects: teamcom.niku.union.persistence.PersistenceException: SQL error code: 0Error message: ERROR: target lists can have at most 1664 entries


This issue is fixed in 15.9.2 and patched in 15.9.1 patch 1. 


  1. Limit the number of columns added in the Per-Period metrics


  2. Shorten the periods set in View Options.


  3. Have multiple browser tab windows open, one for each per-period metric. For example, have one tab with just ETC set in per-period metrics, one tab with just allocation in per-period metrics, etc.

If the above workarounds are not feasible to be used until the issue is fixed, please contact Broadcom Support.

Additional Information

See also: FTE 'Totals' values are incorrect