Custom fields were created inside custom field groups, and those groups would then need to be associated explicitly to every job type, asset type and so on

Because groups were shared across types, modifying a group or it's fields would affect all associations, making nuanced changes per type largely impossible

Fields are created in a central fields settings area, and are visible alongside common system fields

Fields, both custom and system, can be added to global groups, meaning that they will be visible on all entities (i.e. a global asset group will be visible on all assets, irrespective of the asset type)

Fields, both custom and system, can be added to type groups, meaning that they will be visible exclusively on entities of a given type (i.e. a group added to the asset type of "Floor" will only be visible on "Floor" assets)

Because groups and fields are now associated globally or per type it's possible to manage common attributes quickly, or to take a more nuanced approach with different configurations per type

When modifying fields or groups the impact to data on related entities such as jobs or assets was often unclear to the user. In some cases changes only affected new entities. In some cases changes affected all existing entities.

Because fields were effectively bound to groups, it was very challenging to move a field between groups

When modifying fields or groups the changes apply to ALL related entities once the changes are saved. Further, this behavior is now consistent for all entity types, including quotes, jobs, invoices, assets, sites, projects, etc

Fields can be moved fluidly from type based groups to global groups, and visa versa

Fields can be removed from groups, and if there's associated data on a related entity (i.e. a job), then the field will remain available under the Old fields section on the entity

Custom fields could never be truly deleted. Once created

Configuration of custom fields was in many ways a one shot deal. What was created was forever in the system, making it extremely difficult to update the system to meet changing operational requirements.

Deletion of fields is now possible through a two stage process

First, a field can be archived, meaning

Second, an archived field can be deleted, meaning

After deletion, a field name is then released and can be used for new fields

Custom fields could typically be reordered within a group, however groups themselves often couldn't be reordered

Custom fields and system fields could never exist within the same group

System fields and groups would always be displayed first when inspecting an entity (i.e. a quote), meaning custom data, often the most important to users, was pushed all the way to the bottom of the view

The presence of custom fields was rudimentary, in that if a field existed on a job for example, it was always visible. With a lot of fields, this took up a lot of space

Custom fields can be re-ordered within a group

Custom fields can be dragged between groups

Custom fields and some system fields can exist within the same group

Some system fields can be removed

Custom groups and system groups can be ordered fluidly, meaning system groups such as "Visits" or "Description" can be moved to the bottom of an inspector, whilst custom groups can be moved to the top

Custom and system fields can be configured to display selectively, as

Custom groups can have a custom icon configured

The Check all visits option in the Visits filter is now the default behavior

Dedicated Job assignee and Visit assignee filters have been added

Several filters and columns have been renamed

Duration has been added to visit columns

A dedicated Schedule button has been added next to Assign

Duration has been added to the next visit summary

Assign and schedule actions are now available in the wizard

The visit subject and description are no longer automatically populated from the job subject, and instead

When viewing a visit, such as on the agenda, the visit subject is displayed if it has been populated, otherwise we display the job subject

The Google Calendar integration has been updated to work with visits

The Outlook Calendar integration has been updated to work with visits

The asset is moved, then

The activities workspace will be opened in a new tab, pre-filtered to show any incomplete activities associated to that asset

A new filter has been added to facilitate this view Asset ↔ Job location mismatch

Activities can then be selected and moved to suitable new jobs as required

An activity move modal is opened which is pre-filtered to show target jobs that match the new location for selected activities

A suitable target job can then be chosen to move the activities to

If no suitable job is found, a new one can be created

The asset filter now supports matches on nested assets

Several new site columns have been introduced

New icons will progressively be rolled out to mobile apps over the next couple of release

Please note this issue largely only presented on exports

Total cost

Total excluding tax

Total including tax

Total tax

Approved value