Praying review List for different variants

[Annette Kitzmil]

Hello,

So we have several variants in the UI builder based on roles that display different dashboard files based on the role for the variant.  When I click on the tiles in any of the variants, the columns are the same on the preview list

I have been asked and believed I was able to:

1. Have the columns for the preview list when a tile is clicked different for the individual variants because they are role based.  However, if I change the preview column on any variant, they are changed for all.  Is there a way to make the preview columns different for the various role based variant dashboard tiles? If yes, how please?

2.  Also, can the preview list for the various tiles in the same role based variant have different columns or do they all need to be the same?  If they can be different, how please?

Thank you

.

[sreeram_nair]

The issue you're encountering arises from the way preview lists and column configurations are shared across role-based variants in UI Builder. By default, UI Builder shares the same table and list configuration across all variants unless explicitly overridden.

• Create distinct table configurations:

  • Navigate to System UI > Lists or List Layouts.
  • Configure individual list layouts for the table for each role or requirement. Save these configurations with specific names.

• Bind the table configuration to each variant:

  • In UI Builder, bind each role-based variant to its corresponding table configuration by using different Data Resource configurations.

It is also possible to configure different preview list columns for tiles within the same role-based variant.

• Create a separate Data Resource for each tile:

  • In UI Builder, create new data resources for each tile. Define unique column configurations for each resource.
  • For example:
    • Tile A uses Data Resource A with columns X, Y, Z.
    • Tile B uses Data Resource B with columns P, Q, R.

• Bind each tile to its respective Data Resource:

  • While configuring the tile actions (e.g., when the tile is clicked), bind it to the corresponding data resource.