Power BI Builds 5 - Optical Data


Here is my submission for Challenge 5. I will provide a full write up after all the entries have been posted. My objective in this challenge was to provide screens that provided the following info:

  1. Scheduling Info
  2. Medical Records
  3. Age Group Stats

Did a bit more DAX than usual with this one, but was able to get this one done very quickly. Looking forward to seeing all of the other entries!

Here is the link:



@Melissa This is just wow!
Looks like the report covered everything from A to Z.
Excellent submission !

1 Like



I’ve been wondering when you were going to roll out the heavy artillery in one of these challenges, and I guess now I have that answer. This is beyond brilliant, with better functionality then many full-blown commercial scheduling apps I’ve used. And it looks terrific.

I can’t wait to start digging into how you did some of this. It looks like we’re holding off posting the PBIX files until the challenge closes, but can you please post a publish to web link so that we can play with the full functionality of this report?

Absolutely amazing. :clap: :clap: :clap:

  • Brian

Hi uriah1977 ,
Thank you for you for your great feedback. Even though you created an impressive report before I even try to think about creating a report.


Hi @MudassirAli and @BrianJ,

Thank you both so much for your kind words, really appreciate it!
I’m sorry to say I can’t publish to web within my tenant but will definitely share the PBIX file in the final write up after the closing date. :+1:

What I love most about seeing all submissions - is that although we all start with the same dataset - everyone finds a different way to get amazing insights from it and create appealing reports.


Hi All:

Here is my submission for eDNA challenge #5, Optical Data.

I tried to make this “report” look more like an app, so I made minimal use of analytical visuals, instead concentrating on the main “Appointments” page; the secondary “Patients” page was to be accessed as a drill-through target of the “Appointments” page only, and the “Export” page was added to allow not only allow easy export of the patients needing appointments, but one that would “sync” with the main “Appointments” page.



  • made assumption that the optician that did the patient’s last appointment would do the next appointment

Data Model:

  • imported [Optical Data Set.xlsx] as a staging query, and created references in new [Data Model] group for [Patients], [Opticians], [Appointments]

  • [Patients] table:

  • [Opticians] table

    • merged first and last name columns; duplicated column; split columns to re-create first name and last name
  • added [Dates] table using eDNA Extended Date Table M Code;

    • marked as Date table
    • used parameter to get and set start date to Jan 1 of first appointment year
    • used parameter to get and set end date to Dec 31 of the year after this year
  • added [Periods] table using eDNA Period Table M Code (Dynamic Date Range Slicer- Query M); adjusted for “this” and “next” periods (week, month, quarter, year)



  • General:

    • added pages for [Appointments], [Patients], [Export]
    • hid all pages except for [Export] page for so PDF export (in either Power BI Desktop or Power BI Service) will output only the [Export] page
    • added buttons for page navigation to header (font bold white for current, font regular grey for options)
    • added card for [Session Admin] to footer to display last refresh, report ID, report version, report version date (these in card title and whitespace character in card field well)
    • added card for [Report Admin] to footer to display current date, current user (these in card title and whitespace character in card field well)
    • made extensive use of the [General] section in the Visualizations pane to confirm and adjust the values X/Y/Width/Height as necessary
    • used object layering (selection pane grouping) to make the user experience more “app-like” (https://www.youtube.com/watch?v=PKIcjGz_Swg)
    • calculated whether user was accessing report in Power BI Desktop or the Power BI Service and used this info to present tooltips relevant to the user’s environment
      • (used difference between NOW() and UTCNOW() to see if user was on Desktop or Service; I know this is a hack, and doesn’t work if the time in your time zone is the same as UTC, and I would have preferred to use USERNAME() and USERPRINCIPLENAME(), but against my understanding, for whatever reason [perhaps my free PBI license type?], these both gave me the same value irrespective of environment) (*** I’m not happy with this method, I’m still looking for a better way, and would be interested in anyone’s experiences/thoughts/comments ***)
  • [Appointments] page:

    • used standard list slicers complete with “Search” for (Next) Opticians and Patients
    • used “Chiclet Slicer” custom visual for Periods, Age Groups, and Next Appointment Status
    • used “Reset Slicers” button complete with bookmark to allow user to easily return to the original state
    • changed font colour of [Patient Name] column to blue to indicated that you can do something (in this case drill-through to [Patients] page for the selected patient)
  • [Patients] page:

    • used 3 multi-row cards to display General, Appointment, and Personal information for the selected patient
    • set “Patient Name” as drill-through target
    • presented the patient’s appointment history in a table, complete with data bars and up and down triangle icons as necessary to denote a changed right-eye or left-eye value from the previous appointment
  • [Export] page:

    • changed page size to “Letter” and increased spacing from edges in case PDF export was printed
    • used “Chiclet Slicer” custom visual for Periods, Age Groups, and Next Appointment Status
    • sync’d slicers to [Appointments] page to allow export of the patients/appointments that had been selected (via slicers) on the [Appointments] page
    • added PDF Download icon to permit use of the current environment (Desktop, Service) to display the tooltip relevant to the user’s environment

@Greg Good report and great explanation of what you have done in the report. I like the PDF export concept in the report too. I was wondering how you did you calculate the Next Optician for a particular patient.
Are next optician was selected randomly or you used/assumed a particular concept behind this?


1 Like

I just made an assumption.

1 Like


Some incredible submissions so far.

Looking forward to getting into my development today.

1 Like

Below is my submission as Newcomer.

The main goal is to track patient’s appointments.

  1. Did Age Category in Power Query itself
  2. Break down into 2 dimensions(Patients, Opticians) and Fact table(Appts)
  3. Main challenge is to come up with Next Appointment date based on the age, Frequency and the last appointment date
  4. Few measures to get the counts
  5. Conditional formatting to get the flag based on the appointment status

Vision Appointment Tracker


Wow this is good



We are seriously lifting the bar some amazing entries and techniques on display.

Great to see you guys have given me the easy task of having to pick a winner from this lot :worried:

No but seriously some amazing entries and great to see some new faces joining in.

I’m looking forward to reviewing your submissions and sharing some feedback with you.

Any one sat on the fence, there is still time to join in so get involved you wont regret it.

P.S Some great prizes on offer for the new entrants category be sure to check out the post below.

Thanks All


I like the way you structured your report, and showed all of the data that was required. One area I would suggest to improve on is the color theme. This is one thing, even if you are a newbie to Power BI , can help take you to the next level! First of all, I will proclaim that I’m color blind, and without the help of additional tools my report color schemes would be awful. You have a great image in the top left corner of the report. Use this to your advantage, and create your color scheme off this. Here are step by step instructions to help create this.

  1. Go to https://analysthub.enterprisedna.co/colour-theme-generator
  2. Select Image to Colours
  3. Upload your image
    Here is what it came up with:

I also use this website as well to compare:

** All you do is upload your image, and here is what it came back with**

** If you want to take these colors a step farther and create your own JSON theme, go to this site and enter all of the HEX codes: https://themes.powerbi.tips/

Selecting a color scheme is very first thing I do when I’m creating reports. Nothing beats a great first impression!



My Submission to this challenge 5. Tried to create a simple Dashboard with Key information.

Screen1: All Key info about Patient including Upcoming and historical Appointments.

Appoinment Details including overdue appointments and upcoming appointments for effective planning.

Any constructive feedbacks are welcome. #LearningFromEveryone.


Thank you very much for your input and feedback. I am learning a lot with the challenges and valuable feedback from others. This will really help me for next my challenges.



Thank you very much! I have to say, first time on the community, I’m blown away by peoples designs. The standard is amazing.


1 Like


You raise an awesome and very important point here that I think is relevant to the vast majority of us here on the forum. The eDNA content does SUCH a good job on DAX training, that for almost all of us that’s our comfort zone.

However, @nick_m and @melissa have both said something to the effect of (and I’m grossly oversimplifying here) “if something can be done upfront in Power Query, it probably should be”. This was a huge revelation to me, but as I’ve tried to implement it more and more over the past few months rather than just jumping right into DAX, I’ve come to realize that in many/most cases, it is the best approach both from a performance standpoint and also in terms of making your DAX much simpler and easier for others to understand.

Toward that end, I can’t recommend @melissa’s Enterprise DNA TV YouTube Videos highly enough. By working through these in detail (often multiple views per video) and forcing myself in my own work not to jump immediately into back DAX when I struggle with PQ, I’ve started to gain a much more balanced skill set that has been enormously beneficial. It’s hard work at times, but also really rewarding because, while totally different in structure and operation from DAX, M code is incredibly interesting and powerful in its own right.

So, you are spot on in thinking about DAX as just one force among many.

  • Brian

Yep, SQL > PQ > DAX whenever possible.


Once again I look at these and fail to see how they help us to get any better.

I look at the submissions and figure why am I doing this I’m not a graphic artist or a design person.

It’s intimidating at best to us out there that don’t have any design/artistic abilities. What is wrong with a couple of charts and a couple of tables to get the point across.

Sorry but just my feeling on this.


@GuyJohnson It is all about Data Story telling, if your end user can get the idea of what you are showing them in first 10 seconds of seeing the dashboard then your end goal is achieved. You don’t need to decorate a dashboard to make it look good, only few elements related to the data and boom you have a great report, for example someone above used glasses and without even looking at the data I know this report is somehow related to eyes.