Dynamic sorting column in Field Parameter

[JackWren]

Hi, 

I am currently building a report that contains two field parameters. 

The one on the left is to toggle between "Country and Product" : 

Parameter = {

    ("Country", NAMEOF('Country'[Country]), 0),

    ("Product", NAMEOF('Product'[Product]), 1)

}

And the other one is a different one that is used in the matrix as a drill down : 

[Parameter 2 ] = {

    ("Country", NAMEOF('Country'[Country]), 1),

    ("Product", NAMEOF('Product'[Product]), 2),

    ("Segment",NAMEOF(financials[Segment]),3)

}

I wanted to know if it is possible to dynamically change the sort order of the columns in the field parameter 2 based on the selection in the field parameter 1. 

That is to say if we select country, we see this drill down : 

- Country 

- Product

- Segment

If we select Product, we have this hierarchy instead : 

- Product

- Country

- Segment

I don't think it is directly possible as these are tables but maybe somebody has found a workaround there ? 

Thank you 

Kind regards,

[SamWiseOwl]

I feel like the answer is sort of:

It need refining but what I did was join the Top Slicer field to the Field Slicer

In the field slicer I dragged each field in twice

I'm sure there is a more elegant way!

[JackWren · Accepted solution]

Haha, we were on the same track. I tried to also create a relationship between the two tables but I added a key column to link them instead of linking them on the order column. This seems to work in the dummy file but not in my model so I have to compare the two. 

[Parameter 2 ] = {

    ("Country", NAMEOF('Country'[Country]), 1,0),

    ("Product", NAMEOF('Product'[Product]), 2,0),

    ("Segment",NAMEOF(financials[Segment]),3,0),

    ("Country ", NAMEOF('Country'[Country]),6,1),

    ("Product  ", NAMEOF('Product'[Product]), 5,1),

    ("Segment ",NAMEOF(financials[Segment]),4,1)

}

[SamWiseOwl]

Great minds, sadly I was teaching so couldn't respond faster!

I found when. I created a new column assigning the values it crashed when the data was refreshed.

Hence the method of using the name to do the join instead.

Cheers for the Kudos 😁

[SamWiseOwl]

Hi @JackWren 

Not exactly an answer but checking if you knew:
If you put [Parameter 2 ]  in a slicer and set it to multi select, the order in which your user ticks then will define the nesting order they appear in the visual.

[JackWren]

Yes, I know I had this at first but the end users do not want to have to select their own columns. 

And I'm trying to avoid using bookmarks.