Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
hi all,
I have a table with two columns and one row. The first column was obtained by applying To Table to a query.
The result is a datetime and it is supposed to show the time of teh last refresh of the source.
What is very confusing is this:
When I am in the Desktop client I see the right DateTime every time I refresh.
As I save and Publish the report to the appropriate Workspace, I can see the DateTime is GMT (or UTC).
Trying to fix this I did the following:
I created a new column: I subtracted 6 from the Column1 DateTime value as I am EST.
That value shows correctly 6 hours less than the actual EST datetime. When I put that value in my Card visualization in my report and Publish I get a DateTime 2 hours less than it should be.
Anybody has any idea what is happening?
Thanks,
vv
it is supposed to show the time of teh last refresh of the source.
You are solving the wrong problem. That time of last refresh is meaningless. Instead, find an appropriate column in your actual data (Last Modified Date, for example) and use that to indicate data freshness.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 56 | |
| 47 | |
| 44 | |
| 20 | |
| 20 |
| User | Count |
|---|---|
| 73 | |
| 72 | |
| 34 | |
| 33 | |
| 31 |