A few months ago, I wrote a blog about pulling data directly from a SharePoint list instead of relying on a OneLake Sync.

Last week, I found myself wrestling with an issue for my client. The mission? Rebuild a Spark SQL query to create a finance table for reporting their organizational formation. Sounds straightforward, right?

A period to learn, earn a certificate, and connect with the Fabric community. It’s a 50-day journey packed with learning, sharing, and even a contest to test your knowledge.

De wekker gaat. Veel te vroeg. Je ogen voelen alsof ze nog in de beta-versie draaien, maar toch sleep je jezelf richting auto of trein. Daar sta je dan, tussen de files en forenzen, met één prangende vraag: waarom doe ik dit eigenlijk?

Heb jij dit ook wel eens gehad?

Het wachten is beloond: het is tijd om naar de Fabric Community Conferentie Europe te gaan!

Ever run into this? You're working in OneLake files, but you accidentally forget to sign in, and boom, the file doesn’t sync. 😬

Over the past 18 months, I’ve had the opportunity to work with Microsoft Fabric across multiple client projects. During this time, I’ve come to appreciate Fabric as a powerful and versatile platform for data analytics. Yet, one recurring theme keeps surfacing: questions and discussions around how and why I choose different methods to integrate data into the platform.