I love the IDEA of these scorecards in Power BI/MS Fabric, however I feel they are falling short of the mark. Below are some suggestions that I think could help get them to where they should be!
- We use almost exclusively Direct Lake mode semantic models (both flavors on SQL endpoint and OneLake), because these are not refreshed in the traditional sense after I create a goal, the goal is not being updated daily like it is supposed to be. Please fix this, goals should be refreshed based on the frequency I selected at goal set-up regardless of source.
- The Scorecard and Goals APIs need to be updated to allow SPN authentication. Due to the limitation above, I was going to create a script to loop through all scorecards and trigger goal value refreshes, however I cannot do this programitically because SPN authentication is not supported. I was able to hit the APIs and trigger a refresh by "borrowing" my session auth-token; which worked but is not a scalable solution.
- More options for calculation of parent goals based on subgoals. Right now the only options are sum, avg, max, and min. These options don't really work in a mixed metric scenario (e.g. % contact info of 75% and a CSAT of 7.7 out of 8). I think a great addition here would be allow the user to select "Value" or "% of target" like you can in the "Status Rules" area. So you would be able to either take the sum, avg, max, or min of the child values themselves OR take the avg, max, or min of the % of target of the child goals. Alternatively, there could be a way for us to enter a formula for said metrics (maybe even DAX?)
- Provide a way to weight subgoals and take them into account with the parent goal so that we can create a true balanced scorecard. For example, if I had 3 metrics; I could rate one at 25%, another at 25% and the last at 50% contribution. This would also require us to have more flexibility in subgoals calculations (see above)
- Provide an option to show the % of target IN ADDITION to the goal itself
- In the process of connecting a goal and target, allow the user to also select a description that can be mapped from the viz directly or the semantic model (E.g. I have a metric in a semantic model called OSAT with a description of "Overall customer satisfaction metric based on survey".) This could be pulled through directly into a description field for that goal that could be shown as a column and/or a tool tip on hover to give the user additional context
- In addition to the option directly above, allow the user to provide a "manual" description for a goal and target that would be shown if it could not be linked, or they didn't want to link to it
- It would be great if when the user hovers over the menu items it would give them contextual help. For example: Follow goal hover = "Follow this goal to be notified when the status changes or when a check-in is provided. Come back here to unfollow if you no longer want to follow."
- Right now the only viz that allows us to load history on a metric is a trend line at the individual day level, which is rarely used in our reporting. So even though it does work, it is not practical. I would like either:
- The ability to provide an optional report source that a goal would link to when the users clicks the "connected report" link. This would enable me to build a hidden scorecard metric page within a report that would have a metric for tracking purposes but direct the users to the "production" version of that viz I want them to use.
- Or, better yet, allow history to be loaded for other charts as long as they have a date dimension linked to a marked date table
- Allow us to connect prior period values for a given goal as well. These values could be compared to goals in a similar way to target metrics. Ideally you would then be able to see on one goal how you are doing to prior period in addition to how you are doing compared to target. These values could also be options for the "status" rules
- Bugs:
- When I go to "Status Rules" section, if I enter a value (e.g. 80) in the "Value" box then select "% of target" the value gets overwritten and becomes difficult to change. I say it is difficult to change because once the 100 value is there you cannot highlight the whole number and type over, you have to click into the box then use Del and/or Backspace to get rid of the number, then type it again.
- There is some sort of bug when you create a goal that is connected to data, it creates a blank check-in 1 month from the day it was created.
- I see milestones but nothing in the documentation abut what they are, why to use them or how to use them. I feel like they would be useful, but I don't know how to interact with them.
No CommentsBe the first to comment
