on 06-03-2022 10:06 AM
Hi,
i got a problem, that on a chart widget filter, there is no dependent filtering possible.
Only in SAP BW Live Connections based on a query the option "Use query-defined member access" comes available, that reads the query-specific and threrefore Infoobject specific setting how to read the member.
I am using "values as booked".
The query and therefore model behaves totally correct and downfilters without problems in the following:
- BEx query
- AfO
- even on the SAC data tab on a story
- Page filters
What does not work is the depedent filtering in a chart-widget. When going there to the Filters and putting a first selection it takes the query settings - alright.
The second filter does not provide the correct settings then and the query-defined member access function does not do anything. The same setting " only booked values for navigation" is ticked in the backend on all occasions (Composite, InfoObject, Query), but still the full list is displayed.
I am using a navigation attribute as Infoobject and an Infoobject for the filtering. one does not hold any data (navi attribute)
in the screenshots top - BEx/Afo and in the bottom SAC data tab - working as expected. Only the setting on live model "Use query-defined member access" on a chart widget makes problems.
Any ideas?
Yes, as described- a dependent filter, cascading effect. I know it is possible on story filters, input controls, and data explorer as well as data analyzer. and it works there.
Why is SAP not implementing the function normally as expected? Why go a different path only in the chart-widgets? As consultant/customer i really have to question the functionality of the BW Live connection the, if no chart is able to navigate as booked... and the best of all there isnot possibility at all to oversteer the standard behavior. The model/query in the backend tells clearly to show selections on booked values - why is it not being reflected then ...?
All other things work as expected. In my opinion SAP did some shortcut development and forgot some stuff ... intentionally??
In this configuration/status i have to say SAC is a very immature tool. I have witnessed such flaws now in nearly every Live aspect and can say that with a BW Live connection SAC is really not usable after all, if developers (literally) have to guess every time how a chart/component etc. might behave.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi william.yu ,
I recreated the scenario now also for other Composite/Provider/ Queries.
What i question is the behavior of the Chart-Widgets Filters behavior:
Is this now a "feature" or a "bug" ?
For me it feels like a bug, because I in my expectation I tell the query it should filter on the query settings I provided and in every tool that is used (BEx, AO, and even in SAC itself when generating a chart from the data tab) there is a normal dependend DOWNFILTERING happening, ALSO on the Filter Member Selection (see the screenshots bottom). This is NOT the case for the chart-widget filter - no matter what setting i will provide - the chart-widget filter does NOT do a cross-dependent downfiltering of selection values. Even if I tell the setting "Use query-defined member access" to use "only booked values for navigation".
I can technically understand that SAP does restrict the number of requests (by prohibiting many dependent filters and therefore requests) to the backend and that the widget-filter states probably are the ones which are requested once at that point, when asking the modeling initially for the chart creation. But when dealing with live models,i would expect another behavior, that the filters would also reload on every navigation step, since this is the standard behavior. (the query even has the reload on any navigation inside by standard).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess I know what you are looking for. I think you want a 'cascading effect' on widget filter. I'm afraid that's not the feature of SAC at the moment.
Cascading effect only exists for input contorl, story filter and data explorer( the data tab you referred to), widget filter will basically show 'all booked members' or 'all members' according the setting in backend.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.