Forum Discussion
TimeStamp Display - Within the last 2 days
Hi MSparks ,
Based on your clarification that all timestamp values, including historical ones, are now displaying only the time portion in the Lakehouse table preview, and that this change began approximately two days ago this does not appear to align with the previously observed behavior in Microsoft Fabric.
While Spark-based environments can format recent timestamps as time-only, the behavior you're describing suggests there may have been a recent update or change in the Lakehouse UI's rendering logic affecting timestamp display more broadly.
As of now, there is no publicly documented product update confirming this change. Since I do not have access to Microsoft’s internal change logs or engineering channels, I recommend submitting this observation via Microsoft Fabric Support .This will help ensure that the appropriate product team is made aware and can validate whether this is an intended behavior or a regression.
In the meantime, as a practical workaround, you can CAST the timestamp column to STRING in a SQL query to display the full date and time explicitly.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi MSparks ,
Thank you for reaching out to the Microsoft Fabric Community.
What you're observing where only the time portion of a timestamp is shown (e.g., “4:48:08 PM”) is due to how the Spark-based rendering layer in Microsoft Fabric handles recent datetime values during table preview. When a timestamp falls within a recent timeframe (typically the past 1–2 days), the UI may display only the time component.
Please rest assured that this is just a display behavior. The full date and time are still present in your data and remain fully queryable. This formatting behavior is consistent with Apache Spark's default rendering. You can find more detail in the official Spark documentation here: Datetime Patterns - Apache Spark Documentation
While there's currently no configuration option in Fabric to modify this preview behavior, we completely understand how this can be inconvenient especially when monitoring recent data ingestion. We encourage you to share this feedback via the Microsoft Fabric Ideas portal, where the product team reviews feature requests: Microsoft Fabric Ideas – Submit or vote on features
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Thank you for the response v-tsaipranay, but the problem is, that its not just recent dates within the last 1 to 2 days, but every date within the table going back years. As well as the timestamp column was showing the full date and time until 2 days ago.
Hi MSparks ,
Based on your clarification that all timestamp values, including historical ones, are now displaying only the time portion in the Lakehouse table preview, and that this change began approximately two days ago this does not appear to align with the previously observed behavior in Microsoft Fabric.
While Spark-based environments can format recent timestamps as time-only, the behavior you're describing suggests there may have been a recent update or change in the Lakehouse UI's rendering logic affecting timestamp display more broadly.
As of now, there is no publicly documented product update confirming this change. Since I do not have access to Microsoft’s internal change logs or engineering channels, I recommend submitting this observation via Microsoft Fabric Support .This will help ensure that the appropriate product team is made aware and can validate whether this is an intended behavior or a regression.
In the meantime, as a practical workaround, you can CAST the timestamp column to STRING in a SQL query to display the full date and time explicitly.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi MSparks ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.