Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Save of LOCKED CELLS

Locked cells are saved to the database and display the next time the form is opened. Any saved locked cell will only be shown in forms defined with _ALLOC_range(s). In other words, if another form retrieves the same value as saved in a form with ALLOC ranges, the cell will not be locked since the cell doesn't belong to an _ALLOC_ range.

The save of locked cells is user independent. The actual lock is saved to the value entered in the input cell. The lock is only a property linked to the actual data value saved. When Bizview retrieves values to the form, any data value inserted in the form with is_locked=TRUE will be shown as locked in the form (if the FORM contains _ALLOC_range).

Note: The following limitations apply to save of locked cells:

  • Only applied to input cells with CVAL/BV in column and DATA on row (cells that are stored in Bizview database when updating values).

  • No SUM cells (EDITSUM cells) that are locked will be saved and shown as locked the next time the user opens the form.

  • Only input cells with a value are saved to the database. Input cells that are empty are not saved and therefore, any lock in these cells will not be saved either.

  • By default, input cells with a value of 0 are not saved to the database and therefore, any lock in these cells will not be saved either. If 0 values should be saved, tag #SAVEZERO to these cells in the template. In doing so, a cell with a value of 0 and lock will be saved to the database and returned the next time the form is opened.

  • Lock in SPVAL/SPKEY columns will not be saved, since there is no actual record in the database for these columns, they are only linked to each cell value in each row.
Published:

Save of LOCKED CELLS

Locked cells are saved to the database and display the next time the form is opened. Any saved locked cell will only be shown in forms defined with _ALLOC_range(s). In other words, if another form retrieves the same value as saved in a form with ALLOC ranges, the cell will not be locked since the cell doesn't belong to an _ALLOC_ range.

The save of locked cells is user independent. The actual lock is saved to the value entered in the input cell. The lock is only a property linked to the actual data value saved. When Bizview retrieves values to the form, any data value inserted in the form with is_locked=TRUE will be shown as locked in the form (if the FORM contains _ALLOC_range).

Note: The following limitations apply to save of locked cells:

  • Only applied to input cells with CVAL/BV in column and DATA on row (cells that are stored in Bizview database when updating values).

  • No SUM cells (EDITSUM cells) that are locked will be saved and shown as locked the next time the user opens the form.

  • Only input cells with a value are saved to the database. Input cells that are empty are not saved and therefore, any lock in these cells will not be saved either.

  • By default, input cells with a value of 0 are not saved to the database and therefore, any lock in these cells will not be saved either. If 0 values should be saved, tag #SAVEZERO to these cells in the template. In doing so, a cell with a value of 0 and lock will be saved to the database and returned the next time the form is opened.

  • Lock in SPVAL/SPKEY columns will not be saved, since there is no actual record in the database for these columns, they are only linked to each cell value in each row.
For an optimal Community experience, Please view on Desktop
Powered by Zendesk