Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have a table that has a DepartureTime column presented in local. I added a new column that converts this to UTC. I then duplicated the column and changed the type to Date, but when I do, the Date reverts to the date of the local column.
Here's an example; Row 6:
Does anybody have any thoughts/solutions?
Thanks,
Seth
Solved! Go to Solution.
I was able to solve this on my own by converting lcl to UTC and then removing the zone. This allowed me to set the new column to Date without dates reverting to lcl.
I was able to solve this on my own by converting lcl to UTC and then removing the zone. This allowed me to set the new column to Date without dates reverting to lcl.
Unfortunately, while the column appears to be a Date column, it's still a DateTime and so when using that field, a record for each Time shows up. Also, when connecting to another table in the Model view, the results are blank because the date column from my dates table doesn't have times so it will never match on DateTimeZone converted to Date in the presentation layer.
Keep the column types as DateTimeZone during the ETL. Change the format only in the presentation layer (in the visuals)
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
116 | |
104 | |
77 | |
71 | |
50 |
User | Count |
---|---|
146 | |
107 | |
106 | |
89 | |
65 |