It is too late when a user raises the issue that a report is broken. Credibility has already been lost with the very people you are trying to increase report adoption with.

Using Semantic Link Labs in a Microsoft Notebook unlocks a powerful toolkit that allows you to identify issues proactively and can be used to fix many common problems. We will examine the various options for installing Semantic Link Labs and their benefits. All of this is done within the familiar Microsoft Fabric Environment.

Not only can we identify broken reports, but we can also automate the process with notebooks and pipelines. Even if a report is not technically broken, it may be broken from a usability point of view since it does not follow best practices. We can identify those reports so that they can be corrected.

We will cover various tasks that, if done manually, would take more time and aren’t reproducible like code in a notebook is.

A report’s performance depends on the semantic model to which it is connected. We will cover methods for reporting on the semantic model's best practices. By the end of the session, we will have built a semantic model and a report to track the semantic models in our environment using best practices.