Report with a variable number of columns

We do this frequently in reporting, standard use case is to show users a checkbox list of which data they would like to view in the report. The a!gridField's columns parameter is defined as below, utilizing a!applyComponents() to dynamically create the requested columns:

a!applyComponents(
function: a!gridTextColumn(
alignment: "CENTER",
label: _,
field: _,
data: _
),
array: merge(
apply(fn!displayValue,local!columnSelection,local!columnOptionsValue,local!columnOptionsName,null),
local!columnSelection,
apply(rule!reportGetColumnData,local!columnSelection,local!gridData.data)
)
)

2 arrays are used on the report for columns, one for column name (local!columnOptionsName) and one for column field (local!columnOptionsValue). In the merge() above, displayValue is used to obtain the label since the physical selection of field values is stored in local!columnSelection.

For the data parameter, rule!reportGetColumnData is iterated through to return an array of data arrays, rule definition is:

=index(ri!data,ri!column,null)

For more flexibility you can replace the gridTextColumn function under applyComponents with a new expression rule that returns differently depending on field values. Here we may hard code in certain behavior based on the field - users can select any field they like, but if the field being displayed is one with a special case, format it accordingly:

a!gridTextColumn(
alignment: "CENTER",
label: ri!label,
field: ri!field,
data:
if(
or(
ri!field="value",
ri!field="freightInboundTotal",
ri!field="freightOutboundTotal",
ri!field="totalOrder",
ri!field="totalExtendedCost"
),apply(rule!displayPrice,ri!data),
if(ri!field="step",apply(rule!getStep,ri!data),
if(ri!field="priority",left(ri!data,1),
ri!data
)))
)

We do this frequently in reporting, standard use case is to show users a checkbox list of which data they would like to view in the report. The a!gridField's columns parameter is defined as below, utilizing a!applyComponents() to dynamically create the requested columns:

a!applyComponents(
function: a!gridTextColumn(
alignment: "CENTER",
label: _,
field: _,
data: _
),
array: merge(
apply(fn!displayValue,local!columnSelection,local!columnOptionsValue,local!columnOptionsName,null),
local!columnSelection,
apply(rule!reportGetColumnData,local!columnSelection,local!gridData.data)
)
)

2 arrays are used on the report for columns, one for column name (local!columnOptionsName) and one for column field (local!columnOptionsValue). In the merge() above, displayValue is used to obtain the label since the physical selection of field values is stored in local!columnSelection.

For the data parameter, rule!reportGetColumnData is iterated through to return an array of data arrays, rule definition is:

=index(ri!data,ri!column,null)

For more flexibility you can replace the gridTextColumn function under applyComponents with a new expression rule that returns differently depending on field values. Here we may hard code in certain behavior based on the field - users can select any field they like, but if the field being displayed is one with a special case, format it accordingly:

a!gridTextColumn(
alignment: "CENTER",
label: ri!label,
field: ri!field,
data:
if(
or(
ri!field="value",
ri!field="freightInboundTotal",
ri!field="freightOutboundTotal",
ri!field="totalOrder",
ri!field="totalExtendedCost"
),apply(rule!displayPrice,ri!data),
if(ri!field="step",apply(rule!getStep,ri!data),
if(ri!field="priority",left(ri!data,1),
ri!data
)))
)