Global Asset Custom Fields
| Platform: | AvailableWebNot availableMobile |
|---|---|
| Plan Type: | Not availableBasicNot availableEssentialNot availablePremiumAvailableEnterprise |
| User Type: | Not availableRequesterNot availableFull UserAvailableAdministrator |
Global asset custom fields let you create custom fields once, in your Global Organization, and share those fields across your sub-organizations so the same types of assets capture the same custom data everywhere.
With global asset custom fields you can:
- Create custom fields at the Global Organization level and share them with local sub-organizations. For more information, see Create Global Custom Fields.
- Conflict management for fields with the same name. Correct conflicts that happen when you publish a global field to a sub-organization, or when you edit a field's name and it conflicts with an existing field. For more information, see Resolve Duplicate Fields.
- Edit or delete a published global field. Edits are automatically propagated to every sub-organization that uses it. For more information, see Edit Global Custom Fields.
- Convert a global custom field into an independent local field, or promote a local custom field to a global one, without deleting and recreating it. For more information, see Convert Custom Fields.
- Merge local and global custom fields of the same type into a single field, consolidating near-duplicates that accumulate across your sub-organizations. If the fields have conflicting data for the same asset, you can choose which values to keep. For more information, see Merge Custom Fields.
- Filter custom fields by organization, field type, and global or local status. For more information, see Filter Global Custom Fields.
- Ask your MaintainXยฎ representative to import several global custom fields at once using a CSV file. For more information, see Import Global Custom Fields.
- Integrate global custom fields directly into local asset types, so required fields stay locked wherever the asset type is used. For more information, see Use Global Custom Fields with Asset Types.
Requirementsโ
To use global asset custom fields, you must:
- Have a Global Organization with at least one sub-organization. For more information, see About Global Organizations.
- Have a Global Leader user role. For more information, see The Global Leader User Role.
Navigate to the Customize Asset Formโ
To set up global asset fields, you must be in your Global Organization:
- From the sidebar, select the Global Settings menu.
- Select Features. The Features page opens.
- In the Assets section, select Set Preferences. The Assets page opens.
- Navigate to the Customize Asset Form section.
- Select Custom Fields.
Create Global Custom Fieldsโ
To create a new global asset field:
- In the Customize Asset Form section, select Custom Fields. The Asset fields page opens.
- On the Asset fields page, select + New Custom Field.
- Enter a Field Name. The new field name should be unique. Prompts tell you if the field name is available or if it already exists.
- Select a Field Type.
- Select Make this field required if this asset field is required on all asset forms.
- Select Create.
The new field is created at the Global Organization level. However, it isn't shared with your sub-organizations until you publish it.
Publish Global Custom Fieldsโ
Publishing shares a global custom field with your sub-organizations.
To publish a global custom field:
-
If the field is newly created, the details page of the field opens.

A new asset field's details page with no shared organizations -
Select Share with organizations. The Manage assignments page opens.
-
Select the sub-organizations you want to share the asset field with. You can also Select all organizations or Search for organizations that aren't listed.
-
(Optional) Select Automatically add new organizations if you want any new sub-organizations you create to automatically use this asset field.
-
When you have selected all the sub-organizations that will use the custom field, select Next.
-
Select Publish to add the custom field to the asset form of each selected organization.
After you publish, the field appears as a global field in every selected sub-organization. Required can be set by a local organization if it wasn't set by a Global Organization. However, it can't be edited or deleted by the local organization, it can only be edited or deleted by the Global Organization.
If a sub-organization already has a local field with the same name, you can review and resolve any conflicts. For more information, see Resolve Duplicate Fields.
Resolve Duplicate Fieldsโ
When you publish a global custom field, MaintainX checks whether the changes would create duplicate fields with the same name within an organization.
Resolve Duplicates When Publishing a Fieldโ
To resolve a duplicate field during publishing:
- When MaintainX detects a published field with the same name in a sub-organization, the Review duplicates page opens automatically.
- Review the conflicting local custom field(s) and the sub-organization(s) they belong to.
- You can decide if you want to standardize them into global field.
- Select Continue.
- Select Publish to standardize the local field into a global field. This preserves existing data, but the assets using this field will now follow the global field.
The global custom field will always take precedence over the local custom field. In the sub-organization, the custom field is visible in the Custom Fields tab of the Asset Fields page, but is now managed by the Global Organization. Any custom fields managed by the Global Organization are noted as such with an icon. For more information about local organizations and dynamic asset forms, see Dynamic Asset Forms.

Resolve Duplicates When Editing a Fieldโ
If you rename a global custom field to match an existing local custom field in a sub-organization where it's shared, MaintainX flags the naming conflict before saving your changes.
To resolve a naming conflict created by an edit:
- Edit the field's Field Name and save your change.
- The conflict resolution page opens, showing the two fields that now have matching names; the global field you just renamed, and the existing, local field.
- You are asked whether to keep the local field or the global field.
- Select Continue
Once resolved, only one field remains with that name.
Edit Global Custom Fieldsโ
Only Global Organizations can edit a published global custom field.
To edit a global custom field:
-
Select the custom field you want to edit. The details page of that field opens.

Details page of a previously published custom field -
To edit the Field Name, Field Type, or change if the field is required, select (more options) and select Edit.
-
Make the changes and select Save.
-
If your change to the Field Name creates a duplicate of a field already used in a sub-organization, MaintainX opens a conflict resolution page before saving. For more information, see Resolve Duplicates When Editing a Field.
-
To change which sub-organizations the custom field is shared with, select Manage assignments.
-
Edit the shared organizations and select Next.
-
Select Publish to save the changes.
Any sub-organizations using the field update automatically and don't need any action taken in the sub-organization.
Convert Custom Fieldsโ
You can convert a custom field between global and local at any time, without deleting and recreating it.
Convert a Global Custom Field to a Local Fieldโ
Converting a global custom field to a local field removes it from the Global Organization's control, making it an independent, local custom field in each sub-organization that was using it.
To convert a global custom field to local fields, you must be in your Global Organization:
- From your list of Asset fields, navigate to the field you want to convert.
- Select (more options).
- Select Convert to local.
- Confirm the conversion.
The global field is deleted and a new local custom field is created with the same name in each sub-organization that was using the global field. Existing data carries over to each new local field, but the fields are now independent from one another and any future edits to the field in one organization no longer affects the field in any other organization.
Convert a Local Custom Field to a Global Fieldโ
Converting a local custom field to a global field brings it under the control of the Global Organization, making it available to publish to other sub-organizations and making edits to the field easier to maintain across sub-organizations.
To convert a local custom field to a global field:
- In the sub-organization, from the Asset fields list, navigate to the custom field you want to convert.
- Select (more options).
- Select Convert to global.
- When prompted, confirm the conversion.
If no other organization has a field with the same name, the field converts immediately and becomes available to publish from the Global Organization.
If another sub-organization you're publishing to already has a local field with the same name, the conversion doesn't happen and MaintainX tells you a field with that label already exists. To resolve this, either:
- Rename the local or global field so the names no longer conflict, then try converting again.
- From the Global Organization, publish the existing global field to the sub-organization that has the conflicting name instead. This opens the standard flow to resolve duplicate fields. For more information, see Resolve Duplicates When Publishing a Field.
Merge Custom Fieldsโ
Merging custom asset fields in your Global Organization helps you clean up near-duplicate fields that accumulate across your sub-organizations. Merging collapses several fields into a single global field, shared with the affected sub-organizations, while preserving existing asset data.
To merge custom fields:
-
In your Global Organization, go to the list of Asset fields.
-
Select the checkbox of each field you want to merge. They can be local or global fields.
noteYou can only merge fields that have the same field type. The Merge custom fields dialog only lists fields of the selected type.
-
Select Merge. The Merge custom fields dialog opens, listing the fields you selected.
-
From the Merge into drop-down, choose the field your selected fields will merge into:
- Use a selected field: Keep one of the fields you selected as the global field. For more information, see Merge into a Selected or Existing Field.
- Use an existing global field: Merge into a global field that isn't one of your selected fields. For more information, see Merge into a Selected or Existing Field.
- Create new field: Create a new global field to merge into. For more information, see Merge into a New Field.
Merge into a New Fieldโ
Create a new global field and merge your selected fields into it.
To merge into a new field:
-
From the Merge into drop-down, scroll to the bottom and select Create new field.
-
Enter a Field Name.
-
(Optional) Select Required if this field must be completed on all asset forms.
The Field Type is set automatically to the same type as the selected fields and can't be changed.
-
Review the Merge details:
- A new global field is created and made visible in the affected organizations.
- Its name, field type, and settings apply to all merged fields.
- Existing asset data is preserved and visible on the new field.
-
Select Merge.
The fields are merged and the new global field is created.
Merge into a Selected or Existing Fieldโ
Merge into one of your selected fields or into another global field when you want to keep an existing field's name and settings.
To merge into a selected or existing field:
-
From the Merge into drop-down, select a field under Use a selected field or Use an existing global field. Each option shows its field type and how many sub-organizations it's shared with.
-
Review the Merge details:
- The field you chose stays the global field.
- Its name, field type, and settings apply to all merged fields.
- Where an organization has several of these fields, you choose which field's asset data to keep. The others are archived with their history.
-
Select Continue.
If none of the sub-organizations has more than one of the fields you're merging, the merge completes. If any sub-organization has more than one of these fields with data on the same assets, the Review merge dialog opens so you can choose which data to keep. For more information, see Resolve Merge Conflicts.
Resolve Merge Conflictsโ
A merge conflict happens when a sub-organization has more than one of the fields you're merging, and those fields have data on the same assets. MaintainX can't combine the values automatically, so you choose which field's asset data to keep for each affected sub-organization. The fields you don't keep are archived with their history.
For example, suppose a sub-organization has both a Serial No. field and a Serial ID field, and you merge both into Serial Number. You choose which of those two fields' data becomes the data for Serial Number in that sub-organization. The other field is archived.
To resolve a merge conflict:
-
In the Review merge dialog, review the summary at the top. It tells you which fields are being merged, which field they merge into, and how many sub-organizations need your decision.
-
Under Needs your decision, review each affected sub-organization. Sub-organizations with nothing to decide are grouped under No action needed, which stays collapsed.
-
For each sub-organization listed, choose which field's data to keep. You can:
- Select the most used field: Applies the field with the most assets to every pending sub-organization.
- Select a field for each sub-organization: From the Field to keep drop-down, choose a field. Each option shows how many assets it has and whether it's already named for the global field or will be renamed to it.
-
Select Merge. The button is disabled until you've made a decision for every sub-organization listed under Needs your decision, and shows the number of fields being merged (for example, Merge 4 fields).
The fields are merged. In each sub-organization, the field you chose keeps its data and becomes the global field. The other fields are archived with their history.
Delete a Global Custom Fieldโ
Deleting a global custom field removes the field from all organizations.
To delete a global custom field:
- From your list of Asset fields, navigate to the field you want to delete.
- Select (more options).
- Select Delete. The Delete custom field page opens.
- You can choose from two options:
- Delete everywhere: This option removes the field from the global organization and all sub-organizations.
- Convert to local fields: This option removes the field from the control of the Global Organization.
- Select Delete.
Depending on your choice, the field is either removed from all organizations, or reverted to a local field.
Filter Global Custom Fieldsโ
Use the filter options on the Asset fields page to narrow the fields list by:
- Organization
- Global vs. local status
- Field type (for example, single-line text, multi-line text, or number)
Import Global Custom Fieldsโ
Your MaintainX representative handles global custom field imports on your behalf. They use a CSV file to standardize custom asset field names across your sub-organizations or create several new fields at once. Then they publish the fields to your selected sub-organizations in a single pass.
To request an import, give your representative the details for each field you want created:
- Field name
- Field type
- Dropdown options
- Whether the field is required
- The sub-organizations it should publish to
Your MaintainX representative validates the file before importing. Imports can only be reverted right after they happen. After that, the import can't be undone.
Use Global Custom Fields with Asset Typesโ
Global custom fields integrate directly into local asset types. When a global field is selected as required, it stays required and locked wherever it's used, meaning local organizations can't remove it from an asset type. A local organization can set a global field to required for its own asset types even if the field isn't required globally. However, it can't make a required global field optional.
To use a custom field with asset types:
- From the sidebar, select the Global Settings menu.
- Select Features, then in the Assets section, select Set Preferences. The Assets page opens.
- In the Preferences section, select Asset Types.
- Select + New Asset Type.
- Enter a name for the new asset type.
- Select fields from the available asset fields.
- Select Create.
The new asset type is created. For more information about global asset types, see Global Asset Types.