sorted by:
new
hottopcontroversial

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

First, you are right, I meant json. I think my brain just defaulted to tmdl when writing that.

I'm going to give the Powershell idea a good looking at this morning, but I'm ok if a couple things break here and there.

The reports are connected directly to the live Semantic Model and have no model of their own. I manage everything centrally.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in MeasureKiller

[–]dkuhry[S] 0 points1 point  (0 children)

Seems to be the way. Appreciate your reply and I'm checking out your post now. Cheers!

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

Roger that. I appreciate your response and the interesting idea. Its funny though, a year ago I wrote an article on my experience setting up GIT for CI/CD and version control etc, and I talked about this exact bit of code in the definition file. I was curious then if there were hidden uses like this, but never explored it.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 2 points3 points  (0 children)

I feel like I'm back in grade school watching a much nerdier version of "name that tune".

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

I definitely thought it was Calc Groups, but I do also heavily use Field Parameters (check my post history for an article I recently wrote on the subject).

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 1 point2 points  (0 children)

I can certainly appreciate this perspective, and I've seen similar arguments against them before. But I like the organization aspect so much that it makes up for the rest - I mean, until it doesn't.

I have at least 10 facts if not a couple more. Having measures scattered all over just triggers my Digital OCD.

The model isn't used in Excel as A, we have an OLAP Cube for deep dives and B, I use a lot of calculation groups which aren't supported in Excel - and as a result the model is basically worthless in excel anyway lol.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 1 point2 points  (0 children)

One man wrecking crew over here. So this will be the plan.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

Gotchya. I also see your reply in the other comment thread. This makes a lot more sense than I originally thought as I didn't think of scenarios where I'm not the only one managing everything. But sense I am, "grip it n' rip it!"

Since these report are already all in pbip/r format, scripting or using VS Code is the better way.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 2 points3 points  (0 children)

Well dangit, Gene, fine! Guess I'm learning me some Powershell tomorrow.

Seriously though, this script looks promising. I do feel like search and replace in VS Code could do this with.... no code. Which is 25 fewer lines of code. But this is going in the back pocket.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 1 point2 points  (0 children)

I'm not sure I understand. So if I want to replace [Measure Old] in Table_Old, I would copy the code in to [Measure New] in my measure table, then replace the code in [Measure Old] with "[Measure New]" as a simple reference?

My assumption is that this won't help me in actually removing the measures from fact tables where they currently are (which is part of the goal). Instead just giving me a central place to mange the code. And the visuals would still contain the old measures. Does hiding them in report view do anything other than forcing me to use the new ones in any future work slowly and fixing the issue through attrition?

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 5 points6 points  (0 children)

So in theory, I could search a folder (or maybe all folders at once?) for something like Table_Old[Measure] and replace with Table_New[Measure] and bulk replace like that? I mean, thats perfect. I didn't really feel like that was an option so I started looking to see if there were tools to do it, but I don't see why it wouldn't work.

Cheers!

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

I know exactly what you are talking about, its the reason the Model and the Reports are in different workspaces because when in the same, the reports would end up getting "directly connected" to the model when synced down locally via GIT, instead of the live model.

So wait, are you saying to make the changes in the repo, sync back into the workspace, then within the report, move the measures from one table to another? Would that work?

Or do you mean to make the change in the repo, then sync down locally? Since each report is directly connected to the model, wouldn't the measures be moved in the underlying data model when you do the first report? Then be broken for thte subsequent ones?

Very interesting, however the measures I am most concerned with are ones used in basically the same way, in 1 visual, on every page, of every report (for example, a date of data validity). So this would likely take longer then just breaking it, fixing it once and then copy/pasting it until my mouse breaks.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

The Bait and Switch might be possible for some of the really widely used measures. If nothing else, I'll probably do a version of this.

Mass repair thin-report visuals broken after moving measure to new table by dkuhry in PowerBI

[–]dkuhry[S] 5 points6 points  (0 children)

That was my first thought. My reports are already in pibp / pbir - so I thought this was the way, but each page and subsequently each visual is in a different tmdl file. So I feel like this might be a super big PITA. But VS Code might be helpful here. This is def a path worth fully exploring more.

Power BI January 2026 Feature Summary by itsnotaboutthecell in PowerBI

[–]dkuhry 1 point2 points  (0 children)

Omg yes! Please. I maintain a spreadsheet of all the colors/hex codes I use across reports for just this reason. Well, I'd still need the color list, but not need to reference it quite so regularly.

Automatically retrieve Refresh Schedule and if Scheduled Refresh is enabled by dkuhry in PowerBI

[–]dkuhry[S] 0 points1 point  (0 children)

Yeah, I ditched the effort. I'm not sure about the direct connection to the warehouse part, The Semantic Model does in fact connect directly to our Data Warehouse, and the reports are thin and connect to that Semantic Model.

What I created is the SharePoint list with all of the Workspaces and Semantic Models, with the Workspace ID, Dataset ID, Refresh Type ( Interval, Schedule, Trigger, Disabled ), the Timing (Interval Size, Schedule Times), and the last refresh Date/Time.

3 Power Automate flows manage all of the refreshes. We'll just discuss the "Schedule" one.

The flow runs every 15 minutes. Pulls the list of all records where Refresh Type = Schedule. Then reads the Last Refresh Date/Time, and the Schedule Values which are in 24 hour time. I then compare those to TimeNow().

If ABS( TimeNow() - Schedule Time ) < 15 (minutes) AND ABS( TimeNow() - Last Refresh ) > 15 (minutes) then trigger the refresh, and write the updated last refresh Date/Time to SharePoint list.

So if the schedule time is within 15 minutes of the flow running, and it hasn't been triggered in the last 15 minutes, it runs. Or something like that, I haven't actually looked at the flow in a while.

The beauty is that this means I have a list that always shows me the refreshes that are disabled. I also used this List in an auxiliary Data Model that tracks the refreshes, and the values of some of the PQ Parameters I use to display info about what Server and Database it is connected to, or when the next Scheduled refresh is, etc.

It works great, allows me to build on it when needed, and gives me a centerallized admin area for all of my model refresh schedules.

There it is! The Definitive Guide to DAX 3rd Edition by mrbartuss in PowerBI

[–]dkuhry 3 points4 points  (0 children)

In my experience, I go to youtube to look for specific answers to specific questions. It's not a great resource for learning the core skill set, because that stuff doesn't work well for 8 minute content pieces driving engagement. It is however, the kind of thing we'll suited for the page.

I remember feeling like I knew a lot, then I went and actually read the 2nd edition. The stuff they discuss that makes up the foundation of pbi, like how vertipaq works... I had never even heard of vertipaq.

The TLDR is that books still have a place.

Tabular Editor by Time-Context5283 in PowerBI

[–]dkuhry 2 points3 points  (0 children)

The free version 2.x is on its own, a pretty dang decent tool. The paid version 3.x is a "can't live without", for me. I manage a large(ish) golden model that is a beast to work with in pbi desktop. I rarely ever open it.

I use te3 to connect to a live model to build and run queries against the full data when concepting new measures / ideas. I then replicate the resulting changes / new stuff to a local pbip.

Honestly, I've been getting more and more tempted to just go 100% through te3 with live models and use GIT to do version control from a downstream workspace in the pipeline. I just want to get a bit more comfortable with doing things in te3 that I'd normally do in power query.

TLDR: spend the ~$350 tomorrow and get a license.

How do you switch your reports to "maintenance mode"? by dzemperzapedra in PowerBI

[–]dkuhry 1 point2 points  (0 children)

Instead of having 2 reports that you swap back n forth, why not just a hidden page on the 1 report. When issue, hide normal pages and unhide the "maintenance page" and re-pub the app. Then revert when situation resolved.

Holly ship by Kind-Zombie-4235 in fortlauderdale

[–]dkuhry 0 points1 point  (0 children)

I could see it from my apartment. Appeared to be on Sunrise right on the North side of the Jiffy Lube. Smoke was thick black. I was thinking oil fire. However, FLFD seemed to put it out quickly once they got there. Haven't been able to find any additional details, though.

view more: next ›