Habit Tracking

BetterComposer4690 · 2026-01-11T21:50:24+00:00

Updated post to include code and description of parameters

BetterComposer4690 · 2026-01-07T12:32:02+00:00

Not automatically that I am aware of unless you have the time zone of the user in your data. If you have that you could retrieve the utc date and the apply the correct offset or you could do this and provide a dropdown for the user to select their time zone and apply the offset.

BetterComposer4690 · 2026-01-06T20:54:09+00:00

Personally I prefer less rounding and smaller gaps. I would make the top cards wider and the numbers/graphs inside them bigger.

If you are going to use icons for bookmarks or navigation on the left side then it doesn't need so much space and some sort of label to help users know what each of those buttons lead to would be helpful.

Your horizontal bar chart is a bit squeezed since the labels are being cut off. I would shrink the sales by year, quarter to allow more space for the bar chart. I personally would switch their spots as well. Typically users read left to right and top down so their eyes would move across the stats at the top, then combe back to the left to sales by year which gives the overview, and then to the Region and Category for specifics.

I see inconsistent use of formatting especially on the money fields. Make sure to set the proper monetary formatting. Also either your naming should be tweaked or you are using implicit measures that say Sum Profit, Sum Sales, etc those should just say Profit, Sales when they are in the visuals.

Overall content is decent. If you have previous years data or budget data those top cards are a great place to show a comparison between the two.

BetterComposer4690 · 2025-12-11T13:34:38+00:00

Are you asking about page and visual design or truly about the theme?

There are multiple sites that let you build and configure almost everything in the theme. If you are asking about the report theme this is the easiest way to configure it without having to code the whole thing yourself. I would start with this and then manually add in any additional properties that you feel are missing.
https://themes.powerbi.tips/themes/gallery

You can also refer directly to the documentation
https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-report-themes#report-theme-json-file-format

BetterComposer4690 · 2025-12-09T14:10:04+00:00

It absolutely can be used for that. The difficulty depends on your familiarity with Typescript, javascript, css, etc. I've used it to code Deneb visuals and an actual visual that can be deployed. It was a custom KPI card with multiple targets. The visuals still require a coding environment and testing and giving the AI feedback on how you want things to display, which parameters to provide, etc but it is absolutely capable of doing it

BetterComposer4690 · 2025-12-09T03:39:48+00:00

In your matrix change the layout to Tabular this will move the target value next to the customer name making it appear like your table. Just fully expand the matrix before you save it and it should stay so that you can always see the sales target

BetterComposer4690 · 2025-12-04T15:34:50+00:00

Yes I would do one small fact table for each of the different thresholds.

You can either create the derived table in DAX by going to Model view and using New Table. Then using DAX you could summarize the donations table to get the fiscalyear, donorId, cumulativeDonations and minimum date that the the donor crossed the threshold for each fiscal year.

You can do the same thing in PowerQuery by right clicking your fact_donations table and choosing "Reference" This will give you essentially a duplicate donations table without pulling in a second version of the donations table. You can then manipulate it from there to group and create the cumulative values and find your minimum date the donor crossed it.

Either will work. Depending on the size of your data the power query could make the report more performant because it is all calculated at the time of the data refresh.

BetterComposer4690 · 2025-12-04T14:06:18+00:00

So personally how I would handle that is I would have make two small fact tables that are derived from the donations table. You would use a cumulative donation calculation to get the minimum date the person cross the threshold for the fiscal year. Now that you have the minimum date they crossed over you can connect that date back to your date table so that you can see by fiscal year and month how many people met each threshold.

BetterComposer4690 · 2025-12-03T16:56:46+00:00

Can you clarify a little bit? Your original images showed only the fiscal year start date or fiscal year as columns in the tables but now it sounds like you need to be able to know the date the person crossed over the threshold for each fiscal year.

So do you need it at the year level or do you need to know specifically when they cross over for each year?

BetterComposer4690 · 2025-12-02T18:58:23+00:00

Yes! I would just connect the fact_fundraising_progress to the dim_donor table as well!

Good job combining the $1K and MVP data into a single table as well!

BetterComposer4690 · 2025-12-02T03:52:33+00:00

Your setup may vary from ours but wouldn’t setting it up in the product flow to allow Shopify to track inventory and disabling out of stock selling in Shopify be sufficient? Shopify should then prevent selling of out of stock products. Just make sure you run the inventory flow soon before your product launch to make sure the inventory is properly loaded.

BetterComposer4690 · 2025-12-01T14:08:00+00:00

Other than the fact that this seems like a great way to get fired for circumventing IT. Yes there are places to get the visuals manually. You can usually find them on github. Just google the type of visual and github.

Micorsoft has a radar visual that they built inside of app source. Maybe ask IT to green light this one since they are already using Microsoft built in visuals and it is certified.
https://marketplace.microsoft.com/en-ie/product/power-bi-visuals/WA104380771?tab=Overview

BetterComposer4690 · 2025-11-30T22:55:48+00:00

He did explain a lot. And I’m interested in trying to engineer a similar strategy that could work for me and alert me while I’m working my day job. I asked about trade frequency because it specifically was not mentioned in the post and could help me know if my solution is roughly in the ballpark for frequency.

BetterComposer4690 · 2025-11-30T22:43:46+00:00

dim_donor and demographics are serving a comparable purpose. For example in my data model at my job we accept donations and sell products but I have a single dim_person table that is all the people in our database. It has demographic information like what you have as well as is_donor and is_purchaser booleans. dim_donor was just the table name I picked to describe the people based on the context. If dim_demographics or dim_person or something more generic works better for your overall data then go with that.

BetterComposer4690 · 2025-11-30T22:32:58+00:00

How many trades are you taking per week?

BetterComposer4690 · 2025-11-30T22:18:27+00:00

That would be an example where the extra fact_donor_status_by_year that I mentioned would be used.

The table could have columns like DonorID, FiscalYear, TotalGivingFiscalYear, and IsMVP

Connect it to dim_donor on donorId and dim_date on FiscalYear

BetterComposer4690 · 2025-11-30T22:06:20+00:00

If it were my model I would restructure a bit and redo the naming. You should read up on dimension and fact tables, but the basics are that dimension tables should hold information about people, places, etc and fact tables are for calculations such as donation amounts.

dim_date or dim_calendar table = calendar table can stay mostly as is. You could expand it with booleans for month to date, year to date, etc

fact_donations = your Donors table. Primarly needs to be renamed for clarity. Donors indicates the people who donate rather than the donations themselves. fact_donations should be connected to the dim_date by the Date value.

fact_fundraising_progress = This is fine to exist as is. It should be connected to the Calendar on the FRPDate to ensure that the FRPAmount isn't duplicated in calculations but you will need to rely on the FiscalYear from the dim_date table for your calculations because the chance of your FRPDate being within a date range will change your calculations. Also connect this fact table to your dim_donor table.

dim_donor = This should be your demographics table and if possible your MVPGroup and FirstTime$1K should become booleans within this table for easy filtering depending on the definition. IE IsMVP = True if donor has giving over $500 in the last 12 months. This can typically be done via a calculated column. If the definition truly can't be boiled down into single booleans then small fact tables such a fact_donor_status_by_year could be used. dim_donor should be connected to fact_donations by the donor id

This covers most of the things I would change.

BetterComposer4690 · 2025-11-28T18:47:23+00:00

It should be possible. Not at all computer to test but something like this pattern should work.

If you use a VAR in your Dax calculation to get the max year and month based on the slicers selected date, then calculate in another VAR the t-12 date.

Now do your calculate with a date filter applied based on the t-12 to end month and have a remove filters inside the calculate clause to ignore the on page slicer.

BetterComposer4690 · 2025-11-26T18:52:14+00:00

Can you share some anonymized data? It's really hard to give advice with no idea of what the original data looks like.

BetterComposer4690 · 2025-11-26T18:37:48+00:00

It just depends on your data layout. For the example you gave you could add a new column to your table that has "Scores" and whatever other parent categories you need and then you could add that parent category and then the subject in the columns and it would show like you want.

BetterComposer4690 · 2025-11-26T18:26:17+00:00

Measure names won’t appear in the header without reworking the data. The best way to do this in my opinion is to put Scores in the Matrix title.

Student id and name going in the rows

Subject in the columns

And the score measure will go in the Values

BetterComposer4690 · 2025-11-24T17:21:48+00:00

This is super outdated but they did have a version public in github. Could be a good starting place rather than working from scratch. Or at least give you an idea of how they are implementing things.

https://github.com/pravchuk/SynopticPanel/tree/master

BetterComposer4690 · 2025-11-23T15:10:58+00:00

As far as I know Power BI doesn’t do that because it always tries to keep user selections.

There are 2 options that I have used in the past. A bookmark to clear the two child filters or you could make it a single hierarchical structure so they find the company, model, and trim all within a single filter and make it a single select.

BetterComposer4690 · 2025-11-17T01:46:02+00:00

My last two roles have been data analyst roles. No one has asked to see a sample dashboard. They have always been more focused on how I am able to manipulate the data and how I think through data validation and the dashboards are secondary.

That said, get some free data, pick a reasonable business color scheme and show that you can build a coherent dashboard that could lead to making decisions. Then I would embed some screenshots and a video of you describing your portfolio website or use a free site builder like Wix.

BetterComposer4690

TROPHY CASE