Best Practice For Displaying Date/Times in Local Time Zone

Hey Gilbert,

Thanks for the detailed response much appreciated. I will review in detail later today.

On question 1 though I woke up this morning and everything sunk in. You are correct creating the additional columns in PQ will be more effecient. However, this method does require you to create new date/time columns for every time zone your report needs to support. 

If I were to add more time zones to the daylight savings table in PQ and then use calculated columns in DAX to create the local date/time columns I can use a slicer to filter the daylight savings table and reference the offset value. 

Whilst from a performance point of view this will be slower compared with PQ it will be faster and more effecient overall as you are only duplicating each date/time column in your model once. If you were to do it in PQ you need a new date/time column for every time zone you want to support which just gets exponentially large. 

So in summary their doesn't seem to be a "best practice" so to speak. Both PQ and DAX have their advantages/disadvantages. It's up to the architect to think through the model, end user requirements and choose the method that will result in the best performance. 

I haven't tested my theory above yet so I could be completely wrong but it makes sense in my head 😂🤣 I will reply here once I have tested it and proven the theory. 

Cheers,

Fly Kick