cancel
Showing results for 
Search instead for 
Did you mean: 

Cascading Functionality with Dimension Filter Components in Design Studio

0 Kudos

Hello Experts.

I have implemented cascading functionality with dimension filter components.I was able to filter the values based on other dimension filter but the second dimension filter is showing only selected value if I change other selection on first dimension filter.to make this dynamic,every time i'm deselecting the value from 2 dropdown.

please see the below example.

i have 2 dimension filter components 1)Country 2)Region.

1.when I select USA value from Country then i can see all regions which belongs to USA.

2.then i made selection in Region i.e California that's fine.

3.now i was trying to select other country i.e "Australia" from Country Dimension Filter but i don't see dynamic values that are belonging to AUS.instead of this I see the previous selected value.

in this case every time i'm deselecting values from Region then im choosing the value from County dimesnionfilter then i can see all the regions which belongs to selected value

is this design behavior or am i going somewhere wrong?

Accepted Solutions (0)

Answers (3)

Answers (3)

MustafaBensan
Active Contributor

Hi Jagdeep,

I have been able to replicate your issue in both DS 1.6 SP3 and SP4 in SAPUI5 M Mode using a BE Query data source. Just to make sure we are on the same page, here are my results:

1. Application on startup with 2 dimension filters:

2. Select from Filter 1:

3. Filter 1 Result:

4. Filter 2 Selection:

5. Filter 2 Result:

6. In order to select a new Region, Filter 2 (Airline ID) values must now be deselected:

7. Now all Filter 1 Selections are available again:

8. Select a new Filter 1 value:

9. New Filter 2 values are now available:

So in order to see all available values in Filter 1 again, you first have to clear the selection from Filter 2. Frankly, this seems counter-intuitive to me. This behaviour is exhibited with any component that applies data or property binding. I faced the same issue when using property bound multi-select list boxes as well. Now instead of using property binding you populate the list boxes with getMembers() and then apply setFilter(), the above issue does not occur.

Is the above scenario what you have experienced?

Not sure if I have missed a setting or this is by design (which seems unusual) or a bug. Perhaps others may have further feedback.

Regards,

Mustafa.

0 Kudos

Hello mbensan ,

I am working on Lumira Designer dashboards with SAP BEX reports as DataSources. We are also looking for cascading filters functionality as you described in your example. However, cascading functionality is not working in our case. we are using Dimension filters with List as a visualisation mode.

Bex reports are based on SAP ABAP CDS views.

Your help will be appreciated.

Regards

Hari

TammyPowlas
Active Contributor

Hi Jagdeep,

Are you on 1.6 SP4 ?

What is your data source?

If I follow the tutorial here https://archive.sap.com/documents/docs/DOC-49292 I cannot recreate what you describe when I use a BEx query. Maybe you could review the tutorial https://archive.sap.com/documents/docs/DOC-49292 ?

Tammy

0 Kudos

Hi Mustafa,

yes we are on the same page.

I have achieved the same functionality with drop downs. But I haven't tried with list boxes.i hope I can achiveve that also.

I am facing this behaviour with only Dimension filter it seems.

Thank you,

Prasad