Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Anonymous
Not applicable

TImeStamp Column High Capacity Issue

Hello everyone, I have an issue with a Power BI report and its timestamp column. Since the report exceeded the A2 capacity in PowerBi service I checked the Vertipaq Analyzer to x-ray the report in depth. It turned out that the timestamp column comprises 48% of the size of the report in terms of capacity.  What I did was to create a custom column using this conversion function:

= #datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, [Timestamp]/1000)

The conversion was successful BUT I want to get rid of the original timestamp column and keep the derivative date column in order to optimize the report since this timestamp issue hampers the report to be refreshed on PowerBI Service. Any ideas how to that?

Thanks in advance !

1 REPLY 1
ppm1
Solution Sage
Solution Sage

Why not just delete the original high cardinality column? In any case, please see this article for an alternative approach where you split the initial column into Date and Time columns to reduce cardinality (memory needed).

Calculate and Format Durations in DAX – Hoosier BI

 

Pat

Microsoft Employee

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors