Forum Discussion
Fabric Capacity Metrics - Items Operations[TIMESTAMP 2] causes model error and cannot be queried
Hi MarlieHagen
It looks like a regression in the current Fabric Capacity Metrics App the TIMESTAMP 2 column in Items operations is a calculated column whose m expression still references an underlying source field called TIMESTAMP that the latest backend update renamed/removed. That's why the query fails with t66.TIMESTAMP not found (error 10224) everywhere visuals, fabric.evaluate_dax(), and extraction while every other column works.
Workarounds until microsoft patches it:- Update the Metrics App from AppSource and refresh — this class of regression (v47, v53) has historically been fixed in the next release.
- Skip TIMESTAMP 2 and use OperationStartTime / OperationEndTime instead.
- If you can edit the semantic model, fix the M step to point at the current source column.
Thank you,
Srikanth Cheri.CST Team.
Hi MarlieHagen
It looks like a regression in the current Fabric Capacity Metrics App the TIMESTAMP 2 column in Items operations is a calculated column whose m expression still references an underlying source field called TIMESTAMP that the latest backend update renamed/removed. That's why the query fails with t66.TIMESTAMP not found (error 10224) everywhere visuals, fabric.evaluate_dax(), and extraction while every other column works.
Workarounds until microsoft patches it:
- Update the Metrics App from AppSource and refresh — this class of regression (v47, v53) has historically been fixed in the next release.
- Skip TIMESTAMP 2 and use OperationStartTime / OperationEndTime instead.
- If you can edit the semantic model, fix the M step to point at the current source column.
Thank you,
Srikanth Cheri.
CST Team.