Skip to main content

Attributes Groups and fields on entities

How to get the most of out of your attributes and fields on the related entity

Updated over a month ago

In this article, we will look at how to best use and manage system or custom fields/groups on a job, asset, site or any other entity that supports fields.

To learn more about creating field groups or how to add them to specific types, please follow the below links:
​
​Managing Attributes (Global)
​Managing Attributes by Entity Type

--------------------------------------------------------------------------------------

Viewing attribute groups and fields

For the purposes of this guide, we will be looking at a Loc8 Job. However, the functionality below is applicable to any entity that supports system or custom attributes.

Each field group can be expanded or contracted by clicking on the arrow next to the group. Within each group, there may be one or many fields.

Clicking on the field itself will give you a few actions. One is edit, which allows you to edit the field contents if you have the correct permissions and if the field is editable (certain fields like location may not be editable once the entity is created). You will also be able to copy the field contents or view the history for that field.

Searching for Attributes and groups

You can use the search function to search for specific fields or attribute groups. This will not search the contents of the fields, only the field names and group names.

Required fields

If a field is marked as "required", the group it belongs to and the field will always be displayed, even if it has marked as hidden or the group has been contracted. This prevents important fields from being missed.

Removed or Archived fields

If a group is removed from an entity, or if the field itself is archived, but one or more of the fields contained within that group has data, it will be moved into the "Old fields" section. If you click on "Show old fields", it will display any fields with data that have been removed from this entity type.

------------------------------------------------------------------------------------

Did this answer your question?