Path: “_SYS_BIC”. “the cba. Hba. Apps. CRMHLQ/CBAOppsPipelineQuery”
Sent: Friday, March 13, 2015 4:34 PM
Subject: filter in HANA live report
Customer Report has two types of filters:
- Design Time Filter: defined in the Webclient UI. Each column in the bottom HANA Calculated View of the Report hanging can be used as a filter.
- Runtime facet Filter This facet is called Runtime Filter.
The source of this filter: simply put, it comes from the underlying HANA Query View metadata, which is a subset of HANA Query View Association. If an Association item passes a series of tests in the Indian code, the association item appears in the Fiori UI filter list.
After selecting a facet Filter in the Fiori UI:
- Expected Behavior: If this report maintains two types of filter, both must be applied
- Now the client encounters behavior: Only the Runtime Facet Filter is active, while the Design Time Filter is completely ignored.
- According to the code of CustomerReport India that I statically read, they consider the scenario in which two filters work at the same time. According to the code, this function is supported.
- Current problem: None of the 5 HANA Query Views in SAP PreDeliver meet the criteria to be a Runtime Facet Filter, so this problem cannot be replicated in our internal System. We can only debug it in the customer system, or make a similar view imitating the customer’s CBA View on AG3. The metadata here is not view, but the Odata service corresponding to XS, and the association is defined in Odata. Odata of XS needs to be defined separately. It’s confirmed. It’s XS Odata stuff. SAP HANA Developer Guide 2.5.1.2 Tutorial: Add a Repository Workspace But in VS3 (so SAP HANA native standard development things this is the source system) there is.
Then, in HANA Studio, the SAP HANA Development Perspective is used.
Add VS3 system to your systems directory now:
Then add repository as per 2.5.1.2
The diagram below:
For more of Jerry’s original articles, please follow the public account “Wang Zixi “:
