Forum Discussion

MarlieHagen's avatar
MarlieHagen
Frequent Visitor
1 month ago
Solved

Fabric Capacity Metrics - Items Operations[TIMESTAMP 2] causes model error and cannot be queried

Hi Team,

I believe there is an issue with the Microsoft Fabric Capacity Metrics semantic model.

Affected table = Items Operations
Affected column = TIMESTAMP 2
 
Symptoms

The table itself exists and can be queried successfully if you exclude the TIMESTAMP 2 field

If the field is included, this error appears
Expression.Error:
The column 't66.TIMESTAMP' of the table wasn't found.
Microsoft.Data.Mashup.ErrorCode = 10224.
Detail = t66.TIMESTAMP
 

The same error occurs when:

  • Adding Items Operations[TIMESTAMP 2] to a Power BI table visual
  • Querying the table through fabric.evaluate_dax()
  • Extracting the table from the Capacity Metrics semantic model
Could the team please investigate
Many thanks
Marlie
General Comment
  • v-csrikanth's avatar
    v-csrikanth
    1 month ago

    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.

1 Reply

  • v-csrikanth's avatar
    v-csrikanth
    Icon for Community Support rankCommunity Support
    1 month ago

    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.