⟵ hearthere ⟶
  • Training course
  • Creating simple tables and fields
  • Codes base level
  • Selects and links between tables
  • Table settings basic level
  • Prefilters base level
  • Conditional formatting basic level
  • Action codes base level
  • Using pop-up windows
  • Cycles base level
  • Roles and users on the web
  • Table accesses to change, view and visibility in the tree
  • Field accesses
  • Hide and restore mode, access to duplicate rows
  • What are favorite tables, how to make dashboards on the home page?
  • User management
  • Codes advanced level
  • Action codes advanced level
  • Prefilters advanced level
  • Field and table settings advanced level
  • Cycles advanced level
  • Formatting advanced level
  • Select-Tree
  • Executing a scheduled action code
  • Printing and emailing
  • Notifications
  • API interaction
  • Adaptivity and Sections
  • Hide and restore mode, access to duplicate rows

    What happens with a row when it is deleted when "Hide" deletion mode is selected?

    By default, Deletion is set to Delete.

    In Delete mode, rows are instantly deleted without the possibility of recovery.

    There is no undo. For critical tables, you can set a deletion timer or attach a linkToInput call to the deletion trigger, requesting a PIN code input and throwing an errorException if it is incorrect.

    But if you switch it to Hide, the rows will not be deleted — they will be marked as deleted.

    Can it be restored?

    Yes, by clicking the restore button. This feature can be restricted by roles.

    What happens with a Select that uses a hidden value?

    His display will be strikethrough.

    What happens with codes that take values from a hidden row?

    Values from the hidden row can only be taken if the query is where: 'id' = VALUE.

    What should be done with the role, for the user to be able to duplicate rows in the table?

    Duplication and role-based access to duplication.