I can expand one additional level to the decomposition tree after my Field Parameter Field, but if I try expanding any more afterwards than I get "An error occured while rendering the report".
For example:
(Measure ->Year ->Field Parameter -> additonal field) Works 😀
(Measure -> Year -> Field Parameter -> Addtional Field ->Attempt to expand additional field) Broken ☹️
11 Comments
- BBrak
Advocate I
It seems this issue still isn't solved more than 4.5 years later. The odd thing is that although I added a Field Parameter (#dimParameter - 1) to 'Explain by', Power BI added a distinct field, Sales category on top of that.
- NA32Frequent Visitorthe issue is still there, i was trying to do it but is doesn't work on the third level
- FlavioMeneses
Advocate II
This is still an issue. Any plans on fixing it? - OlivierBigotRegular Visitor
Hi,
I've been trying to setup a decomposition tree that should allow a vast range of "explain by" fields and came accross the same.
I setup a parameter which has 300 values, I add it in the explain by section of the decomposition tree, upon selecting the first value for my first "explain by" it work, then once I click the + button and select a second value, nothing happens.
Another interesting thing is that it's limited to 150 values, when I'm adding my parameter, the + button only lists the first 150 values instead of the full list.
Could you please have a look and make it work, it would be of great value for many of us to be able to let our users choose how they're going to explain by their data from a predefined list as adding items into the explain by one by one is a hassle and they cannot even be ordered.
Regards,
- AnonymousNot applicable
Same issue 1.5 years later the 1st time it was reported.
When you are using a field parameter as 'Explain by' to provide flexibility to your report consumers to analyse the data, the PBI crashes.
Crashes occur in multiple occasion:
- when trying to expand to a 3 parameter layers
- when expanding to 2 layers and clicking on an item in the 1st layer to expand that
This is a bug that is simple to reproduce and requires solution from Microsoft
- NZPowerBIGuyNew Member
I am getting the same issue. Drilling down twice past a field parameter. causes the report rendering to break.
- AnonymousNot applicable
Same error for me, it worked for 2 level in fields parameter and crashed at 3rd level. Some one please provide workaround or fix asap
- ljt5Frequent Visitor
It's right, same exact error here. I can use 2 parameter fields, the 3rd crashes. Please someone could check this? It is very easy to reproduce this error
- INS-GwylimRegular Visitor
I am trying to use a field parameter on the Explain By input of my decomposition tree.
It is not working as I thought it would.
Firstly, why do I use a field parameter in the Explain By input?
I want the fields from the field parameter to be show in the drill into options when clicking the plus sign buttons.
There are some fields in the field parameter that are excluded for certain users by RLS or by certain selected values, so I don't want those fields to show up in the visual.This works. Yey. Except...
The visual is not allowing me to pick the fields in the order that I want.
No matter which field I select to drill into next, it always (seems) to pick the next field in the order set in the field parameter order columns.It also seems to get stuck after picking up to 2 or 4 dimensions, I'm not able to drill into more dimensions or to remove the already open dimensions using the cross sign button on top of the decomposition tree either.
In Power BI Desktop when trying to remove the field parameter from the Explain By input, I am getting an error and it won't be removed and need to remove the whole visual.
I published my report to the Power BI service to see if maybe it's just buggy in Power BI Desktop, but in the Power BI service it's also not behaving well. - AnonymousNot applicable
Same exact issue here! With Field Parameters it only expands two levels and crashes on the third.
It doesnt happen if i manually include the fields in the chart, the problem is when using Field Parameters.