General Question: Documentation

[holgergubbels]

Hi Community,

I have a more general question: I work for several customers, coaching them in building good semantic models or create them myself. Some of my models are quite complex. Sometimes I stumble over my own models, for example, when I think I have forgotten a relationship or power query deleted the relationsship because I changed a field in the transformations.

Documentation is a frequent requirement (which is never really fullfilled). How do you document your semantic models and your decisions? For sure I can put comments in a dax measure. But this is not sufficient when it comes to relations, to inactive relations or the interplay between measures, filters, tables and so on.

Thanks for your opinion!

Holger

[speedramps]

I edit the semantic data model.

Then click [Enter data] to add a new table and call it Amendment History with the following columns:-

Date, time, author, change request ref and description of the change.

I then create a hidden page in my reports that display the Amendment History.

The table is published with the semantic data model to the Power Bi Service.

Any team member can then see the reason for the latest changes, providing all team members always update the table when they make changes.

It also helps it there is also a documentation on Jiri, DevOps or any other change control system with a corresponding "change request ref".

Encouraged team members to use a check lists to check each other’s work before (or immediately after implementation) to ensure that documentation, naming standards and other best practices have been followed.

Please click thumbs up for this suggestion, 👍
and [accept solution] if it works.
You can accept multiple solutions. 😀