eye-low-vision--Manage Column Visibility

Overview

In the Avonni Data Table, you don't have to show every column all the time. Using the Hidden attribute, you can create a "Smart UI" that automatically reveals or hides columns based on specific data conditions or business rules.

This tutorial moves beyond simple permissions and shows you how to use Contextual Visibility to keep your interface clean and focused.


General Concept

Column visibility is controlled by a Boolean (True/False) formula. This formula acts as a toggle for the "Hidden" property:

  • If Formula = true: The column is Hidden.

  • If Formula = false: The column is Visible.

Note: It helps to think of this as the "Hide Condition." If the condition is met, the column disappears


Use Case: Conditional "Discount Justification"

Imagine you have an Opportunities table. You allow sales reps to offer discounts, but if a discount exceeds 15%, company policy requires them to complete a "Justification" field.

To keep the table clean, you want the Justification column to be hidden for standard deals and visible only when a high discount is entered.

Guided Steps

1

Create the formula

On your Dynamic Component, create a formula variable of type boolean. This formula will evaluate to true or false and serve as the condition for the Hidden attribute. If the formula returns true, the column will be hidden; if it returns false, the column will be displayed.

In this example, we want to hide the column for users whose profile is not System Administrator or Sales Manager. Here’s the formula syntax:

This formula returns ‎true (so the column is visible) when the current user’s profile is System Administrator or Sales Manager, and ‎false (so the column is hidden) for all other profiles

circle-check

Pro Tip

2

Map the formula

Map this Boolean formula variable to the Hidden attribute of the margin column in the Data Table.

3

Save and test

Save your changes, then open the table as a System Administrator and as another profile to confirm that the margin column behaves as expected

Last updated

Was this helpful?