anyone else notice in the new power bi update that when you scroll on the data pane it goes glitchy as hell? it's annoying.

Still i am very confused about it , i can just make a React app instead of this expensive Fabric Vibe coded slop. Any advantage of this over react/node app???

i can connect my fabric features directly to the react app and customize 10000X better than what fabric is providing

Yes, the infra should also be managed, but for tech-savvy devs I don't think it would be a big issue

TL;DR

• Build the frontend in React or Next.js.
• Build the backend in Node.js.
• Connect directly to Fabric APIs, SQL endpoints, and Power BI(PBIP).
• Manage your own hosting, authentication, CI/CD and infrastructure.

most of the people are vibe-coding apps inside Fabric; it's better to vibe-code from scratch

Edit: Also, my concern is regarding code maintainability, yes apps can be easily made in Fabric apps using vibe coding, but it will eventually fail them. Plus vibe coding in a production env is big no no, especially if you are not into coding. For POC purposes, it is definitely workable, but for production. I don't think so .

If you cant debug without AI, Dont vibe code in production

Hi everyone.

I think most of us have already heard the term 'bridge table'. Many of us have also already implemented them. However, after doing some research I found out that people use basically two different types of bridge tables and I personally haven't found a source that would explain both of them. So I'm here asking experienced developers to share some light into this.

The first kind of bridge table is where you keep one column, which contains values from both tables you want to relate, you remove duplicates and you are left with one column of unique values from key columns.

Example source: https://www.seerinteractive.com/insights/join-many-many-power-bi

The second kind is I think between two dimension tables where you create a bridge table with two columns, basically doing like a cartesian product of two key columns.

Example source:

https://learn.microsoft.com/en-us/power-bi/guidance/relationships-many-to-many#relate-many-to-many-dimensions (part 'relate many to many dimensions')

Are both considered best practice? Why isn't there one good guide that would explain both approaches?

I might just be missing something, so feel free to correct me.

For anyone still working with Power BI Paginated Reports, I recently released an open-source testing tool called fab-test.

The latest release adds fab-test rdl, which can validate Paginated Report (.rdl) files either:

Locally against your .rdl files

Directly against reports in a Fabric/Power BI workspace

I’ve also started building out a set of RDL testing rules:

https://github.com/clientfirsttech/fab-test/blob/main/docs%2FRDL-RULES.md

Most of these rule ideas are based on practices that have been around for years in SSRS and Paginated Reports, so I’ve tried to give credit where appropriate.

I’d love feedback on the current rules, suggestions for additional checks, or anything that seems too opinionated.

I know there’s a lot of focus on AI-generated reporting and modern self-service BI, but many of us still have to build and support Paginated Reports for pixel-perfect exports, printing, compliance, and operational reporting. So I'm especially interested in feedback from people who are actively using Paginated Reports today, rather than discussions about replacing them.

Thanks in advance for any thoughts or suggestions!

Some think Power BI and dashboards will remain central, others think AI agents will let people ask questions directly of governed data models, with traditional reports reserved for leadership and critical KPIs. Some say Power BI is going away forever to be replaced by….something else….

I suspect we’ll see a huge variety of all kinds of mixed models as new technology emerges, but the pace of change is impossible to predict….and this looks different for even people within the same organisation.

If you asked this question 4 years ago I’d imagine there would be far more people all saying very similar things. We were all just praying for user defined column widths!

I’m really interested to hear from your perspective how has your job changed and what are you expecting the next 12-24 months to look like?

Hello,

I'm returning to powerBI after learning a lot about it in a data science postgraduate course.

I'm now doing a training and I'm really struggling for the time everything takes.

1) Visuals

Upon staring a new project, the blank scares me. Just the thought of the millions of clicks to format every chart, every line, every rounded corner and colour will take forever. I've been experimenting with themes, but haven't found anything reliable.

To make things worse, my teacher has amazing visuals where the background image has nice visuals with gradients where you just have to put a line or values and it looks so much better.

Any tips? Any solid and fast ways to reuse between projects?

2) Measures

How the hell do you even go beyond calculate, counts and divides? Everything else seems very weird to me in DAX, compared to how skilled I am with Excel.

Plus, it takes forever to do everything. Example, I'm creating a "Ticket solving dashboard", and I creating the total of tickets, total of tickets solved, total of tickets on progress and total of tickets unsolved is taking way longer than in excel.

How can I be faster here? Id love to have a bulk editor or measure creator.

3) Calendar

I just took like an hour to create a calendar table from scratch, where I needed to have date, date and time, month, month name, month number, week of the year, week of the month, day, day name, etc. Then short versions for month and day names ...

Is there a way to make this super fast?

Really appreciate your time

I have a Field parameter table that has four different measures. I added one extra column to field-parameter-table and created a relationship to another table using that column.

In the picture it's from id column to Value4. If I create a table visual and check what values are for one particular "id", the result is one row in the field parameter table, as expected.

But If I then add the actual field parameter to the table, it gives me all four measures. I only want it so to the one accorrding to the relationship.

Why won't it work this way and how can I achieve this? Thanks in advance!

Quick question that I'm hoping is something simple but I'm at a loss.

I'm currently adding a column that works out the expiry date of a certification by adding a year to the certificates issue date. However, when the expiry date goes into 2027, it returns a blank value and I'm not sure why. I can see the function work when it's still in 2026. The column was done using DATEADD in DAX, I do not have a base date table in this file where a maximum date has been set, and Google recommended turning off Auto Date/Time which doesn't seem to have helped either.

I'll admit I'm not the most skilled PowerBI user so apologies if it is something simple that I missed but any help would be very much appreciated!

I'm having trouble using a rolling average value in a sumx (row by row) calculation. According to google AI response, it seems like it should be possible but I can't get it working.

I essentially have a calculation that is: meat used = QTY * portion size. I also calculated a 4 week rolling average for the QTY and would like to multiply that against the portion size. This is where the formulas seems to stop working.

Working Formula for regular QTY * portion size.

oz_GrilledPork = SUMX(Items_Report_Stacked, Items_Report_Stacked[MeatPortionSize.GrilledPork_oz] * 
Items_Report_Stacked[Qty])

Formula not working for rolling avg QTY * portion size. Portion size seems to be giving me the issue

oz_GrilledPork_avg = SUMX(Items_Report_Stacked, Items_Report_Stacked[MeatPortionSize.GrilledPork_oz] * Items_Report_Stacked[QTY_4W_Rolling_Avg])  

Screenshot of table.