Category: Microsoft Fabric

Kenneth Omorodion generates a snapshot:

In most modern businesses, by default, operational systems are managed in a way that only shows the current view of things in their data like active tickets, open incidents, active complaints, and daily sales. While this is a great way to monitor day-to-day reporting, it however tends to hide an important narrative for the business. For instance, it does not show how things have changed over time. It also does not tell a story on how previous periods compared to the current, in terms of the actual state of the data.

So, without a snapshot view implementation, there is no way to accurately view when data changes, and this may lead to a loss of the previous view forever with no way to retrieve that snapshot.

Click through to see how.

Ed Lima makes some data available to other tools:

In today’s data-driven world, the ability to quickly expose data through modern APIs is crucial. Microsoft Fabric’s API for GraphQL combined with Materialized Lake Views offers a powerful solution that bridges the gap between your Fabric LakeHouse data and application developers who need fast, flexible access to your data.

In this guide, we’ll walk you through how to create a materialized view in a Lakehouse and expose it through a GraphQL API—all within the Microsoft Fabric ecosystem. This approach gives you the best of both worlds: the performance optimization of materialized views and the developer-friendly querying capabilities of GraphQL.

I’d say one interesting reason for why you might want to do this is to feed data to products like Teams, Power Automate, or Copilot Studio. In those cases, having the data be accessible via GraphQL makes it easier than working with finicky connectors that may or may not exist.