vdl-datagrid-column
Define an array column within a <vdl-datagrid>
. Must be contained within a <vdl-datagrid>
element. You can also add <vdl-datagrid-column>
elements associated with index sets in the datagrid to allow customization of the index columns.
Example
<vdl-datagrid>
<vdl-datagrid-column entity="MY_ARRAY_1" editable="true">
<vdl-validate pass="=value > 10">Value must be greater than 10</vdl-validate>
</vdl-datagrid-column>
<vdl-datagrid-column entity="MY_ARRAY_2">
<vdl-index-filter set="MY_INDEX_SET" value="=2"></vdl-index-filter>
</vdl-datagrid-column>
</vdl-datagrid>
Attributes
bottom-calc | Specify a built-in calculation, one of avg, max, min, sum, concat or count to show that calculated value, alternatively provide a custom function, as a dynamic expression.
|
since 5.2 | accepts expression | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
class | CSS classes to add to the table column cells. You can provide multiple classes separated by spaces. | since 5.2 | accepts expression | ||||||||||||||||
disable-set-sorting | When applied to an index column, this will prevent set sorting from being applied to the column. Default table sorting will be used instead. It will also exclude this column from the default list of sorted columns. This option is provided to reduce the sorting overhead where performance is being affected. Set the value to "true" to disable set sorting for this datagrid column. | since 5.2 | |||||||||||||||||
editable | Whether the cells within this column are editable. The column will automatically switch to read-only whilst the bound scenario is reserved for execution. | since 5.2 | accepts expression | ||||||||||||||||
editor-checked-value | The value to set the cell data to if input type is checkbox and it is checked. | since 5.2 | |||||||||||||||||
editor-options | An expression that results in one of the follow to be used as the select options: an array of values, an object of property to value or an array of objects containing key and value properties. This will automatically set the editor-type to be select.
|
since 5.2 | requires expression | ||||||||||||||||
editor-options-include-empty | Allow array elements to be removed using the select input. Setting this to true will add a blank item to the top of the select list. | since 5.2 | |||||||||||||||||
editor-options-set | Name of a set entity to use for select options. This will display labels if a labels entity is defined against this set. This will automatically set the editor-type to be select. | since 5.2 | |||||||||||||||||
editor-type | The editor type to use, in edit mode, for cells in this column. If not specified then it will be autodetected based on entity type. Possible values: checkbox, select, text. | since 5.2 | |||||||||||||||||
editor-unchecked-value | The value to set the cell data to if input type is checkbox and it is not checked. | since 5.2 | |||||||||||||||||
entity | Name of the array entity to show in this column. Throws an error if the entity doesn't exist or is not an array or set type. | since 5.2 | |||||||||||||||||
filter-by-formatted | Use formatted values for filtering. This defaults to false unless the entity has a label in which case the default is true. | since 5.2 | |||||||||||||||||
format | Specify a number formatting string. Only applicable to array elements of type integer, real, decision variable and constraint. The formatting syntax is explained in the Xpress Insight Developer Guide. | since 5.2 | |||||||||||||||||
heading | A custom header for this column, will default to be the entity alias. Alternatively, you can set the title as the text contents of the <vdl-datagrid-column> element. | since 5.2 | accepts expression | ||||||||||||||||
render | Reference to a custom cell renderer. Overrides any default entity rendering. This will be used to generate the cell value for rendering, filtering and sorting. It must be an expression and resolves as a function, this function should return a string. Render callback may only reference entities through VDL expression that are not present on the table. If it is necessary to use entities data from other columns, then rowData array must be used in the render callback.
|
since 5.2 | requires expression | ||||||||||||||||
scenario | The scenario id/index for this column. Not allowed on index column (when specifying a set entity). This attribute will not affect the scenario variable in the render expression. | since 5.2 | accepts expression | ||||||||||||||||
set | Name of the set entity to show in this column. Throws an error if the entity doesn't exist or is not a set type. | since 5.2 | |||||||||||||||||
set-position | Index (zero-based) of occurrence of that index set in the index tuple for the array. Defaults to next available position. | since 5.2 | |||||||||||||||||
sort-by-formatted | Use formatted values for sorting. This is always set to enabled for calculated columns. | since 5.2 | |||||||||||||||||
sort-direction | The direction the column data should be sorted in. | since 5.2 | |||||||||||||||||
sort-order | Sets the column to be sorted by default, provide a number from 0. With multiple sorted columns the number provides the order in which sorting should be applied to the columns, so the highest number will result in the column having sorting applied last. | since 5.2 | |||||||||||||||||
width | The width, in pixels, to set the column. | since 5.2 | accepts expression |
Element contents
Text content only
The text contents are used as the column header. If the "heading" attribute is specified it will override the text contents as the column header. It can also contain multiple <vdl-validate> tags, which are used for column value validation. Validation is performed on initialisation and on every change.
© 2001-2023 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.