⟵ 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
  • Codes advanced level
  • Action codes advanced level
  • Prefilters advanced level
  • Field and table settings advanced level
  • Cycles advanced level
  • Formatting advanced level
  • Extra buttons in the context panel
  • Additional pictures and texts in the right-click panel
  • Using texts replace the field value
  • Block adding or deleting by the number of rows in the table
  • Hiding fields by conditions
  • Displaying buttons in the rows part
  • Select-Tree
  • Executing a scheduled action code
  • Printing and emailing
  • Notifications
  • API interaction
  • Adaptivity and Sections

    • Hiding fields by conditions

    Example of hiding fields in panels and mobile interface

    Hiding in the panel with the ability to show based on a condition:


    f1=:     setFormat(hide: "panel" = true)

f2=: setFormat(condition: #type = 1; hide: "panel" = false)

    Hiding in the panel without the ability to show and excluding from column distribution:


    f1=:     setFormat(hide: "extpanel" = true)

    Hiding in the mobile interface:


    f1=:     setFormat(hide: "mobile" = true)

f2=: setFormat(condition: #type = 1; hide: "mobile" = false)

    Example of hiding the columns of the rows part by conditions

    Hiding a field in web follows a slightly different path — it is done through table formatting and the fieldhide parameter of the setTableFormat function:


    f1=:     setTableFormat(fieldhide: 'field' = true)

f2=: setTableFormat(condition: #h_type = 1; fieldhide: 'field' = false)

    Is this hiding strong or weak?

    This hiding is weak — the user can open the field settings and show them.