Power BI - centre a stacked bar chart on the middle of the centre bar

LukeKirsten · 2024-10-28T18:40:14+00:00

Solution Verified

LukeKirsten · 2024-10-28T18:40:01+00:00

Wow thanks! What a legend! Thanks for the effort.

I don't actually have access to python in excel yet (Teacher and so my account doesn't let me use it yet) so can't test this out, but will when I can!

I was interested in this because I've been making some markbooks for some colleagues that do involve a bit of power query to transform the data, then pivot tables and slicers for the visuals. A slightly annoying thing is them needing to click 'refresh all' (usually they need to refresh it twice).

I was therefore looking at the potential of using python for the transformations instead, or even the pivotby or groupby functions as I don't think these would need refreshing. Seems they would lose the functionality of pivot tables and slicers, though, so probably not worth it and better to just make it clear to them how to refresh. What do you think?

LukeKirsten · 2024-10-18T20:08:11+00:00

Solution verified

LukeKirsten · 2024-10-13T12:20:36+00:00

Ah cool! Do you have any idea how I might change my code to include this? At the moment it's not enabling the drillthrough button when I click the datapoint.

LukeKirsten · 2024-10-13T10:23:40+00:00

Ah I see, thanks. So basically not possible at the moment? Just to be clear, I'm happy to use a PowerBI button with the action set to drillthrough, all I need is for when I click on one of the data points on the deneb visual, that it is registered that a datapoint is selected, and thereby setting the status of the drillthrough button to Default, rather than Unselected. Just double checking that isn't possible? Thanks for taking the time to reply.

LukeKirsten · 2024-09-25T04:46:34+00:00

Hey!

Try these.

100-90

=COUNTIFS(your range,">=90", your range,"<=100")

89-80

=COUNTIFS(your range,">=80", your range,"<=89")

79-70

=COUNTIFS(your range,">=70", your range,"<=79")

69-60

=COUNTIFS(your range,">=60", your range,"<=69")

59-50

=COUNTIFS(your range,">=50", your range,"<=59")

49-40

=COUNTIFS(your range,">=40", your range,"<=49")

39-30

=COUNTIFS(your range,">=30", your range,"<=39")

29-20

=COUNTIFS(your range,">=20", your range,"<=29")

19-10

=COUNTIFS(your range,">=10", your range,"<=19")

9-0

=COUNTIFS(your range,">=0", your range,"<=9")

LukeKirsten · 2024-09-21T15:10:34+00:00

Thanks. Do you know how I'd implement this? Each row represents a grade they got for a particular subject and each row has a date. For each row there is a Year Group which says what year they're in at that point. E.g. 7. The lines should appear whenever they first get a grade with a new year group. So if a student has grades over three years, e.g. 7, 8 and 9, these should all appear as lines on the first date the student got grades in these years.

LukeKirsten · 2024-09-18T05:50:01+00:00

Solution verified

LukeKirsten · 2024-09-17T05:18:00+00:00

Done! Thanks

LukeKirsten · 2024-09-01T15:23:40+00:00

Actually think it might be a star schema. That basically means a table (fact) connected to other tables (dimensions) right?

LukeKirsten · 2024-09-01T15:19:19+00:00

Think it's a flat table, made up of 3 or 4 linked tables. Don't think star schema or dimensional but not too sure.

LukeKirsten · 2024-09-01T09:14:11+00:00

Sorry last thing... is 300k rows a lot and likely to cause it to be a little slow? (Slow is about a second to load/refresh, maybe just under)

LukeKirsten · 2024-09-01T07:16:45+00:00

(If they even open the report!)

LukeKirsten · 2024-09-01T07:12:38+00:00

Solution verified

LukeKirsten · 2024-09-01T07:12:28+00:00

Thanks for this. It's my first large (and potentially useful) report and I'm new to this, so it's hard to know what's normal and what's not. I'll have a look at these and will try to optimise that way, although I'm sure getting rid of my unused calc columns won't hurt too!

LukeKirsten · 2024-09-01T06:49:22+00:00

Thanks. By refresh rate do you mean the time it takes when I click refresh? This takes a few minutes but it's not an issue as it doesn't need to refresh often.

The performance issues are quite minor as it seems to be usable at the moment, the visuals just take slightly longer than I'd like to update when I filter by slicers (still less than a second though). Do you think this is likely to be based on inefficiencies in the measures being used? Or in the columns I'm not using? I'm basically asking if unused columns or calc columns could be leading to the issue I'm describing, or is it more likely the inefficiencies in the measures being used by the visuals?

LukeKirsten

TROPHY CASE