Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
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 !
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
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 4 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 16 | |
| 12 | |
| 9 | |
| 7 | |
| 6 |