Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello everyone,
We have a Dataverse shortcut in a Fabric lakehouse.
We've noticed that the times are not the same between the data in the Dataverse (for example, a date field has the value 2024-01-31 22:42) and the operation of the shortcut in Fabric, where the same date has the value 2024-01-31 21:42.
I imagine this is because the Dataverse is in West Europe whereas the Fabric capacity/tenant is in North Europe.
However do you have any idea how to correct this without doing timezone conversions.
Thank you in advance for your help,
Vivien
Solved! Go to Solution.
I am assuming you leveraged 'Fabric link' in dataverse to create a shortcut in fabric lakehouse. With this setup, your tiemstamps would be converted to UTC. You can checkout this video for more info
https://www.youtube.com/watch?v=-qWvy_-lNgI
You need to transform your timestamp columns to an appropriate timezone
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|
Hello,
Isn't there a more acceptable solution? Isn't it possible to keep the times as they are in the data source?
Thank you in advance for your feedback,
Hi @vivien57 ,
Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.
If these also don't help, please share more detailed information and description to help us clarify your scenario to test.
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
I am assuming you leveraged 'Fabric link' in dataverse to create a shortcut in fabric lakehouse. With this setup, your tiemstamps would be converted to UTC. You can checkout this video for more info
https://www.youtube.com/watch?v=-qWvy_-lNgI
You need to transform your timestamp columns to an appropriate timezone
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|
User | Count |
---|---|
6 | |
2 | |
2 | |
2 | |
2 |
User | Count |
---|---|
18 | |
17 | |
6 | |
5 | |
4 |