⟵ hearthere ⟶

Strikethrough selects and what it may be caused by

selects_table
Set bookmark

What happens if the line referenced by Select is deleted?

If a value of a row that has been deleted was selected in the select field, you will see a strikethrough basis.

What if a value was selected when it was available by condition, and then it is shown crossed out because the condition is not met?

Similarly, the crossed-out basis will be displayed if, according to the current selection conditions, this value has become unavailable. To avoid this, the select is built not directly through where, but through id with the addition of the current value to this list:


=:
selectRowListForSelect(table: 'table'; field: 'name'; where: 'id' = $listAdd) listAdd: listAdd(list: $list; item: $#nfv) list: selectList(table: 'table'; field: 'id'; where: 'condition' = #condition_field)

What is hiding instead of deleting and how are such rows displayed?

Sometimes table configuration may imply that rows will be hidden rather than deleted — in this case, they can be restored and the data from these rows remains accessible via select with the condition where: 'id' = ....

When a deleted row's value is selected, it will be displayed as strikethrough display!

This strikethrough is controlled by the parameter is_del: true, which we encountered earlier.

What happens if you build a select by select?

In this case, we will see the values of the second select as displays. What if you choose available values in the first select, and specific ones in the second:


=:
selectRowListForSelect(table: 'table'; field: 'name'; where: 'id' = #first_select) // this is the select code for the second (dependent) select // the table is the same for both the first and the second select

So we select from the source table only those values that are chosen in the first select.