Custom fields let you add your own data points to devices, beyond the built-in fields like serial number or purchase date. Each organization defines its own set of custom fields, and every active field can carry a value on any device.
When creating a custom field, choose a type:
Text - short text, up to 500 characters.
Textarea - longer text, up to 5,000 characters.
Number - a numeric value.
Date - a calendar date. The date must be a real one (for example, February 31st is rejected).
Select - a value chosen from a fixed list of options you configure.
A custom field needs:
Name - required, up to 100 characters.
Description - optional, up to 500 characters.
Required - whether every device must have a value for this field.
Sort order - controls where the field appears relative to others. If you don't set one, new fields are placed after all existing fields.
Select fields need at least one option (up to 100), and options can't repeat, including case-insensitive duplicates (for example, "US" and "us" can't both be options on the same field).
You can rename a field, change its description, reorder it, or turn it on/off at any time.
If you change a field's type or its select options, AssetBolt checks that every value already stored for that field still fits the new definition. If any existing value would become invalid (for example, removing a select option that's currently in use), the update is rejected until those values are cleaned up.
Each value is checked against the field's type before it's saved:
Number fields must contain a valid number.
Date fields must contain a valid calendar date.
Select fields must match one of the field's configured options.
If a field is marked required, a device must have a value for it. Required values can't be deleted individually, only replaced.
When you submit values for several custom fields on a device at once:
Each field can only appear once in the submission.
Every field referenced must be an active custom field on the organization.
Required fields are checked against the combined set of values already stored on the device and the ones you're submitting, so you don't need to resend values that haven't changed.
Deleting a custom field removes it and its stored values from devices.
