How to use styling rules in your table widget & notes on performance – SAP Analytics Cloud
The content section of a styling rule defines the application of the styling rule on the table. We can define the relevant context for the styling rule. Using the mouse button on the right top corner, we can pick and select the desired context in the table widget itself.
Using the options below we can adjust the rule:
- Data: The data column consists of checkboxes for each dimension in the table drill. The story designer can opt to style transactional data. If the story designer opts the checkbox. transactional data for all selected member (as part of the context) will be styled.
- Header: The header can also be opted. Selecting the header, will also style the members (of the chosen context). Hence the style will be visible in the master data section.
- Member: The shown number provides the story designer the information how many different dimension members are considered (as part of the selected context). Hovering over the number will result in displaying the selected member descriptions. Note, this number can be adjusted using the context picker on the top right corner. In case a story designer wants to modify the context, it can be adjusted directly in the table.
- Level: The chosen relation provides the story designer with the flexibility to style hierarchical relations of the selected context.
- Self: Self means, the selected member that is part of the picked context anyway. “Self”-member can be seen by hovering over the number of members (see point 3).
- Self & children: Using that option we can also style children of the member. In case the chosen member is a node in a hierarchy, all immediate/direct children underneath the selected member will also be styled. In other words: The style will be directly applied to the direct descendants of the picked member, too.
- Self & Sibling: The option to style siblings will also result in styling selected members having the same parent member in the hierarchy.
- Self & descendants. This option is like 4.2. Not only direct descendants will be styled, but also all hierarchy levels below will be styled, too.
- Children & Descendants: same as 4.2 and 4.4, but without Self 4.1
- All: This will style the whole context of the dimension
Read-only: The applied style will make affected cells input disabled.
Editable: The applied style will make affected cells input enabled.
Notes on performance
As a best practice we recommend styling rules over ad-hoc styling. To learn more about ad-hoc styles, click here. Styling rules support CRUD (create, read, update, delete) which makes them modifiable and ready for generic use. Note, styling performs faster the less rules are defined and the less members are used in the content definition.
Thanks for the blog. One follow up question: Is it possible to apply the same styling rules to multiple tables? Not, styles, but the rules.
thank you for the very interesting presentation of the topic. I would have one question, could you explain how you craeted this setting marked in red?