Skip to main content

Custom fields

This page allows you to manage custom fields for various data entities in Alvao (tickets, services, etc.).

Options:

  • Command panel
    • New custom field - Add new field.
    • Edit - edit the selected field. The menu contains the same commands as the blocks in the field preview.
    • Delete - delete selected fields.
  • Custom field table - the table contains views for each entity (Ticket, Service, SLA, ...) that show the custom fields of the entity. You can customize the table as needed.
  • Selected field - when you select an field in the table, a preview will appear to the right of the table with information about the selected field. In each preview block, the Edit command is displayed to edit that block.

Limitations​

Because custom fields data is stored in database table columns, both the number of custom fields and the amount of data are limited by Azure SQL Database (Microsoft SQL Server) constraints.

  • Maximum number of custom fields per entity: 1,000
  • Maximum table row size: 8,060 bytes
    • The row size is calculated as the sum of the data sizes of all columns. Custom fields with the nvarchar(n) data type typically contribute the most to the row size. What matters is the actual size of the stored data, not the maximum capacity of the data type. For example, the row size of four nvarchar(4000) custom fields depends on the real length of the stored text. If all fields are null, the row size is 0 bytes. If each field contains 1,000 characters, the row size is calculated as: 4 (fields) * 1,000 (characters) * 2 (bytes per Unicode character) = 8,000 bytes. If you need to store longer text in a custom column, it is recommended to use the nvarchar(max) data type, as its data is stored outside the table row and therefore does not count toward the row size limit.