Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hey all,
Short of it, I have a BOM Lines report that displays the BOM header on the top and the BOM lines in a separate visual on the bottom. My users need to "drill down" the BOM lines. This means they need to see the BOM lines for BOMs inside the BOM header. I think most developers from a manufacturing background will understand that! There is an undefined number of levels that the user can "drill down." So, I can't do that with just a separate tab.
Is it possible to open another report from a report with a filter set by a record in a visual? Is there another solution I am not thinking of?
I can write Python if needed but I have zero experience developing for PBI. I could do this in less than an hour if I could write in X++ and wire a button!
Full context: My company is migrating 20+ sites into one ERP. Access to the old ERP's legacy data is still needed, but the license to the legacy ERP is set to expire. I've been tasked with creating reports to view the legacy data, and the service/engineering users require this behavior from the report. I could tell them to open a new BOM Lines report in a separate tab and filter there. However, this gets cumbersome. I have created a full Indented BOM paginated report. However, exploding an entire BOM all the way down for these large machines takes around 10 minutes. And the service person jump needs to know what pump is inside an assembly.
Sounds like Power BI is not the right tool for your scenario.
Have you considered decomposition tree visuals?
First, thank you for your reply! I'll play with decomposition tree visuals tomorrow and see if I can make it work. From first glance of the MSDN it may work. If it does, I will accept this as the solution.
And I agree, it's probably not the right tool. However, it's the tool I am being required to work with. It is odd to me that this is not a feature already, though. I enjoy PBI, but I am running into a lot of gaps that are head-scratchers for me.
User | Count |
---|---|
5 | |
4 | |
3 | |
2 | |
2 |
User | Count |
---|---|
8 | |
6 | |
4 | |
4 | |
4 |