Ordering of Visual Filters in Analytical List Page

[former_member600789]

An Analytical List Page application lets you analyze data from different perspectives, investigate a root cause, and to act on transactional content. You can identify relevant areas within data sets or significant single instances using data visualization and business intelligence. All this can be done seamlessly within one page.

ALP contains visual filters to provide an intuitive way of choosing filter values from an associated measure value.

An application can have multiple visual filters. This article will explain how we can change the ordering of these visual filters.

 

The default view of the visual filter bar is based on the filter fields defined in the UI.SelectionFieldsannotation for which a visual filter is defined.

Initially, lets assume that we have 4 visual filters as described in the below image.



Notice that the current ordering is

1. Planned Costs by Cost Element


2. Actual Costs by Cost Center


3. Difference by Date


4. Actual Costs by StringDate

Now to change this ordering, we need to change the ordering of these filters in UI.SelectionFields in the annotations of the main entity set. It will look something like this.

The first visual filter title (planned costs by Cost Element) correspond to CostElement in selection Fields. This applies to rest of the entries also.

Just change the ordering of these fields. Eg, I have changed the first two values in selectionFields. It will look something like this.



That's all you had to do. You can go back and see the visual filter bar. It will look something like this.

Note: Many times it is possible that an entry in SelectionFields does not correspond to any visual filter. In such case, that entry will be ignored and its next entry will be considered. Eg. TotalProperties here does not have any visual filters assigned to it, thus it will be ignored and next entry, that is, DisplayCurrency will be taken into consideration.

Note: It may happen that there are two UI.SelectionFields present inside a common target. Then in such a case, the union of elements of both selectionFields will be considered. Eg. The below two annotations are technically same.





Note: It may also happen that there are repeated elements in multiple SelectionFields inside a common target (as seen in below pic).



Here, CostCenter and CostElement are present in reversed orders in both SelectionFields. In such cases, union of unique elements in both SelectionFields will take place and for repeated elements (like CostCenter and CostElement), the order present in last SelectionFields will be applied.

Conclusion:

Visual Filters can be a great help as chart visualization enables you to understand data more easily and become aware of relevant data faster. having one or more visual filters allows for quick analysis of the data set. Also, we could change the way the filters behave by changing the SelecionFeild annotations.