SAC Application Designer Read Elements of Universal Display Hierarchy 1DG_2 in Table

[axel_]

Hi All,

we use a lot of BW live queries that utililize the BW universal display hierarchy (UDH) feature.
It is working fine to display in SAC tables however we observe when we want to work with the data elements of the UDH in scripting the hierarchy in SAC is artificial (1DG_2) and not representing real dimension members that you can utilize for filtering other widget etc.

Is there a way to translate the 1DG_2 dimension member keys back to real dimension member keys?

Thanks for all replys in advance!

Best regards,
Axel

-------------------------------------------------------------------------------------------------------------------------

If you use SAC with BW-Live-Connection you might want to vote for following improvement requests:

Table: Break line for BW Query key figure / Fixed word wrap in query should be represented in SAC table (BW Live Connection)https://influence.sap.com/sap/ino/#/idea/235012

Ability to save story without pre-selecting mandatory prompts
https://influence.sap.com/sap/ino/#/idea/251755

Option to open Stories/Apps from Catolog in a new TAB + Full Screen/Present Mode
https://influence.sap.com/sap/ino/#/idea/253514/?section=sectionDetails

Browse option when selecting data sources in Data Analyzer
https://influence.sap.com/sap/ino/#/idea/263949/?section=sectionDetails

BW Live connect w/o model (transient access like in Data Analyzer)
https://influence.sap.com/sap/ino/#/idea/228641

SAP Analytics Cloud - Analysis for Office Repository
https://influence.sap.com/sap/ino/#/idea/260246

Datapoint commenting for BW Live models

https://influence.sap.com/sap/ino/#/idea/273160

------------------------------------------------------------------------------------------------------------------------

[former_member816950]

Hi Axel,

Unfortunately it's not able to get the dimension member keys according to your demands currently.

It seems to be a new feature enhancement with some effort, and not be solved in a short time. So I would suggest to use model without UDH firstly to work around.

Thanks
Catherine