Challenge 13 - Acing Documentation!

Apologies all for the delay.

The revised Due Date is: SUNDAY 23rd MAY 2021 (PST)

Sorry for the confusion.

Have updated the post.

Thanks,
H

1 Like

All,

I wanted to let everyone know that the First Time Participant Prize is back up for grabs this challenge. This is our equivalent of the “Rookie of the Year” award, and was when future Data Challenge stars like @Alvi, @bradsmith and @Neba first popped up on the radar screen. To try to encourage more members to jump in and participate in the Challenges, we are offering the following choice of prizes to the top member first-time entry, as judged by @haroonali1000 and the Enterprise DNA Team:

  1. a copy of the Definitive Guide to DAX, 2nd Edition (the indispensable "bible"of DAX) or your choice of any other book from the eDNA Forum Recommended List ; or
  2. a copy of SnagIt 2021, a do-it-all screen capture and graphics tool used by the members of the expert team for screen grabs, annotation, gif and video generation, photo editing, etc. @nick_m got me hooked on this, and it has a million and one uses for Power BI report development; or
  3. a four-month subscription to FlatIcon.com - this is an online service with millions of downloadable and editable icons that you can use to really polish your Power BI reports.

As someone currently in the midst of a job change, I can tell you that this Challenge is IMMENSELY practical. If you develop Power BI reports as part of your job, at some point you WILL need to fully document all your reports to successfully transition them to the next person responsible for development and maintenance. Even better, by developing great automated documentation reports using tools like the DataMarc documenter, you can document all your current reports in real time, rather than having to go back and do a bunch of them during a time of transition.

Participation in these Challenges will pay back the investment of time manyfold in terms of the enhanced skill you will gain quickly, while building a great professional portfolio. But the chance to pick up a cool prize along the way is also nice. :grinning:

So, we hope to see a bunch of new faces in the Challenge entries this round, in addition to the stalwarts.

Good luck!

  • Brian
1 Like

@haroonali1000,

Question came up today during a JMAP Zoom call on the Challenge. In terms of building out improvements to the DataMarc documentation report, those improvements can be done manually as an example/protytpe? (i.e., they don’t have to be automatically implemented for any report that’s run through the tool, nor do we necessarily have to provide a path for how that could be done in a generalizable way, correct? ).

We were 95% certain that’s how you’re interpreting the challenge requirement as well, but had enough lingering doubts that we thought it worth asking the question.

Thanks.

  • Brian
1 Like

Hi Brian,

You are spot on the changes can be manual and all are welcome. Really is just about a sharing of knowledge and hopefully get everyone thinking about how they can provide excellent documentation.

Thanks,

Haroon

1 Like

Hi, I was able to install and run this, however I encountered maybe some errors, for example, “Query ‘Tables’ (step ‘Renamed Columns1’) references other queries or steps, so it may not directly access a data source. Please rebuild this data combination.” that are blocking some dependent queries. Anyone can tell me how to overcome this blockage?

05/20 update: I found the issue is connection string calculated from the parameters. Hard-coding it resolved the issue.

@haroonali1000 Here is my entry!

Take a peek here!

6 Likes

Hi All:

I wasn’t able to come up with enough ideas worthy of pursuit for Power BI documentation for C13, so I won’t be submitting this iteration. What I did have some success with, however, was to leverage the JSON files directly that are either components of a PBIX file or that can be extracted using Tabular Editor to audit a PBIX file.

The JSON file for the model behind the [Financial Reporting in Power BI] PBIX (as extracted by my version of TE2) is over 5800 lines.

The JSON file for the layout of the [Financial Reporting in Power BI] PBIX (as retrieved from unzipping the PBIX) is over 1300 lines.

So far, I’ve been able to make it parameterizable (sp?) to allow it to access the extracted JSON files behind any PBIX and to display info about several entities, including:

  • Tables
  • Columns
  • Relationships
  • Partitions
  • Measure groups
  • Pages
  • Resources (images, themes)

As I could not nearly properly investigate this potential method and extract useful insights within the time frame of this challenge (nor share my thoughts and solicit/incorporate comments/thoughts from other members of the eDNA forum/experts), I plan to continue my efforts and post again when and if I produce something that might be useful.

Greg

Hello all!

Here is my entry for Challenge # 13. It was quite a challenge to imagine a documentation report!
Thank you for setting this up @haroonali1000 ! I will certainly continue to explore and think about this use case.

Spoiler alert






14 Likes

WoW!!

Amazing report as always @alexbadiu

1 Like

@alexbadiu,

bill gates supa hot fire

OMG - this is absolutely unbelievable!

Unfortunately, it’s totally unusable as a documentation report, because the first question the client would ask me is “why is the DOCUMENTATION so much better than the report you built me?” :laughing:

Absolutely cannot wait to read your writeup on this one.

  • Brian
8 Likes

Hahaha! Thank you for your comment, Brian! It made me laugh :laughing:

4 Likes

wow… @alexbadiu,

You should do a video on how you did it a step by step instructions along with written. it would be interesting
thanks
keith

2 Likes

@alexbadiu I think @BrianJ summed it up perfectly, stunning!

1 Like

Who said documentation is boring :rofl:

2 Likes

Absolutely incredible Alex

3 Likes

Beautiful and lots of great details! I hadn’t seen a side panel like that before, so great!

I also like your approach to this in that it’s a tailored report on this report including details about who created it and the timeline to deployment, showcasing what is involved in creating a report (it’s a little bit inception but I like it!). Fantastic way to drive home the point that it should have an audience and be validated too. The details page is also wonderful with all the screenshots too. Performance data too and full column level best practices!! Just wonderful!

7 Likes

Hi @haroonali1000

This is my late entry for this challenger.

Summary

Online Version

Documentation - jbressan.pbix (311.0 KB)

7 Likes

Wow, @alexbadiu this is super star level stuff. Your submissions are always super, I think you should put in some videos to show us how you go about some of these things :slight_smile:

2 Likes

Aspirational. Amazing.

2 Likes
2 Likes