I’m fetching data from Salesforce and storing it in a Lakehouse using a data pipeline. However, after the data is stored in the Lakehouse, I’ve noticed that the values in the DateTime-type columns are shifted—specifically, the timestamps are 4 hours ahead compared to the source data in Salesforce. During my investigation, I’m wondering: does Microsoft Fabric automatically convert DateTime values to a specific time zone? Based on my analysis, the 4-hour difference aligns with the time zone offset between UTC and EDT. Although Salesforce operates in the EDT time zone, it stores and processes DateTime values internally in UTC. If anyone has encountered a similar issue, I’d appreciate it if you could reach out or share your insights. Thanks!!

Hi All, I have created a schema in Lakehouse and loaded the data into it using a pipeline. --> In Lakehouse view : all the tables are created like schema --> In SQL EndPoint : all the new tables are moved under dbo schema. any help/suggestions to fix this and move the tables to newly created schema. Pipeline: lakehouse SqlEP

Ive had this issue on an off for a while and cant figure it out, ive tried using: df.write.format("delta").mode.("overwrite").save("File/path") and I get the result in the Screen shot. When I use .SaveAsTable, I get an error. cant figure it out! Surely writing as a delta either works or it doesnt, I still get a delta log and a parquet, but its like its not recognised?? has anyone come across this and know more from the error response? bonus question, where do you go for diagnosing errors? thanks!

Hi There. Is there a way to share my powerbi report with users in my company that do not have powerbi pro lic like for them to view the report i'm sharing? If so how? How can Power Automate or SSIS help?

Cleared the certification! The community here was a huge help. Thanks for creating this, Will! I'm excited to learn more advanced scenarios and contribute to the community.