Adding and deleting fields

In this article, you'll learn how to add and delete fields from a flexible asset template.

There are several kinds of fields available to help you structure data in flexible assets. For more information, see Flexible asset field definitions.

Prerequisites

  • You need Manager or Administrator level access to IT Glue.
  • If you plan to import data, make sure your data is formatted for our field types.
  • Run a backup (Account > Export Data) before deleting anything, so that you have a place to roll back to if something goes wrong.

Instructions

Adding a field

  1. Click Account from the top navigation bar.
  2. Click Flexible Asset Types from the sidebar.
  3. Click the pencil icon to the right of the asset you'd like to add the field to.
  4. On the next screen, scroll down and click + New field button.
  5. Give the new field a name and choose the field's kind and other attributes.
    From the moment you create a new field, it's possible to change any of the options. However, once that field is in use, editing the "kind" attribute will be disabled.
  6. Drag and drop the fields to change their order, if needed.
  7. Click Save to save your changes and add the field to your form.

Deleting a field

  1. Click Account from the top navigation bar.
  2. Click Flexible Asset Types from the sidebar.
  3. Click the pencil icon to the right of the asset you'd like to delete the field from.
  4. On the next screen, find the field you want to delete from the flexible asset.
  5. Click the Remove field under the field settings for the field.
    Warning. Any fields that are grayed out contain data. If you delete any of these grayed out fields from your flexible asset, this will completely remove the field. So if you have lots of entries connected to this field, all of this data will be permanently deleted. You can use the list views in Global > Assets to see the data before you delete it.
  6. Click Save to save your changes and delete the field from your form.
Was this article helpful?
1 out of 1 found this helpful