Custom Fields for Items

What are they and what are they for?

An Item Custom Field is an extra field that you define, which automatically appears on the Create / Edit Item form, alongside the standard fields (Name, SKU, Price, etc.). Once you create it, every item can have its own value for that field.

Unlike other custom-field catalogs (such as the ones for Accounts or Contacts), the same Item Custom Field can appear on the Items, Services and Kits forms independently: you choose on which of those three forms each field shows up.

This feature is useful when you need to store data specific to your business that is not part of AdmCloud's standard catalog, or when a developer is building a plugin or a custom integration that needs extra information on your items.

How to use it

1. Open the screen. Go to Item Custom Fields from the Customization menu.
2. Create the field. Enter the Field Name, the Label users will see, and the Data Type. Check which forms it should appear on: Visible on Items, Visible on Services and/or Visible on Kits.
3. Save. The field is immediately available on the forms you checked.
4. Fill in the value on each item. When creating or editing an Item, Service or Kit, complete the new field along with the other data and save as usual.
5. Review or edit the field's definition. From this screen's list you can open any field to review its configuration or edit the data that can still be changed (see "What you can't change" below).

Key capabilities

• The same field can be shown on Items, Services and Kits independently, so you don't need to create a duplicate field per product type.
• Supports simple data types (text, number, date, yes/no) as well as references to other entities in the system, a Custom List, or a Custom Record.
• Can be marked as required and carry a suggested default value.
• Can be protected so only its owner can view and edit the field's structure.
• If your company is part of a group of companies, the field's owner can transfer (copy) its definition to another company in the group.
• Also available through the REST API (list, create, edit and delete) for external integrations.

Key fields

Validations when saving

• Field Name is required, with no spaces and no special characters.
• Field Name must be unique: you cannot reuse the same name on two item custom fields.
• Label is required.
• Owner is required.
• If the field is "Protected", only the Owner can save changes to its structure.
• The Default Value must be valid for the chosen Data Type (for example, you cannot enter text in a numeric field).
• Custom Record is required when the Data Type is "Custom Record", and cannot be set if you chose a different data type.

What you can't change after creating it

To protect the information already captured on your items, once you save the field for the first time the form locks editing of these three items:

• The Field Name.
• The Data Type.
• The associated Custom List.

If you need to change any of these, create a new field with the correct configuration instead of editing the existing one.

Deleting a custom field

Deleting a custom field also deletes the values captured on every item, service or kit that had it filled in; this action cannot be undone. The system also blocks deletion if the field is being used by a plugin, and lists which plugins depend on it so you can review them first.

Transferring the field to another company

If your company is part of a group of companies in AdmCloud, the field's Owner can transfer (copy) its definition — along with its associated Custom List, if any — to another company in the group, without having to recreate it manually. This option only appears on the field's Details screen for the user who created it, and is not available in companies still in their evaluation period.

Availability, plan and permissions

• This feature requires the Enterprise plan. If your plan does not include it, the option won't appear in the menu and the screens will show a "not available in your edition" message.
• Access is controlled by the "Customization" permission on the user group, with separate levels for view, add, edit and delete.
• A field marked as "Protected" can only be viewed and edited by its Owner (ForTech users are not subject to this restriction).

Changing the field without editing the record

Normally, changing the value of a custom field means opening the record for editing, changing the data and saving. The Allow changing it in consult mode checkbox offers a shortcut: the field is also shown enabled on the consult screen, just like Status and Group on Service Requests.

It is useful for follow-up data that changes over time and is not part of the record's main content: the status of a task, who reviewed it, an internal classification, and so on.

What happens when you turn it on

• On the consult screen the field is no longer greyed out and is drawn with its normal control (dropdown, search box, checkbox, text box...), depending on its Data Type.
• When you pick or type the new value and leave the field, the change is saved on its own: there is no Save button and the page is not reloaded. AdmCloud shows a confirmation notice.
• If the save fails, the field goes back to its previous value and the error message is shown.
• The change is recorded in the record's log, like any other modification.

Who can use it

• Only users with edit permission on this screen. Everyone else still sees the field as read-only.
• Only on the data types captured with a list or a selector. It is not available for Rich Text or File, because those fields need their own capture flow; if you pick one of those types, the checkbox disappears from the form.

Tips and common pitfalls