Renaming and Hiding Aeon Client Fields

Follow

Renaming Aeon Fields Video

The Field Customizations table in the staff manager allows staff to rename or hide fields from grids and forms in the Aeon client. This feature allows staff to hide sensitive data and rename custom fields. This feature is based on the layout templates described under Creating and Assigning Templates to Staff Users; changes made using this table become the new "default" system settings until the original, "out of the box" default settings are restored to a user from within the staff manager. Restoring the settings to default from the client does not alter these settings.

Understanding Field Names

The Field Customizations table contains a Field Name field for you to enter the fieldname, from the client form, that you want to rename or hide. Note that you are entering the actual fieldname, and not the name as it is displayed on the client form. Because field customizations apply to more than just database fields, and practically all of the fields in the client can be renamed or hidden, the easiest way to locate the field name for a field that you want to rename or hide is to view it from the Customization window on the client form. This is handy for composite fields that are generated in the client and not part of the database.

For example, the fieldname for the Name field in the User Information section of the Request form, UserFullName, is a combination of the database fields FirstName and LastName. Equally, Notes is listed as UserNotes and NoteType is listed as RequestNotes.

Remember, the name as displayed on the form is not what you want to enter as the Field Name value.

Some fields cannot be hidden or renamed, and some should be hidden or renamed with caution.

  1. The Clearance Status field and the Status field used in Email grids cannot currently be renamed or hidden.
  2. While you can rename or hide the Location, Reference Number and Creation Date fields, be aware that doing so hides or renames those fields on the Request Forms, Activity Forms, User Records, and Transactions.
    • For example, if you want to change all the fields called ID in the Tracking table to User ID, then any fields with the keyword ID in the Activity Form will also default to User ID. This occurs even when the field name may be slightly different such as Bib. ID since it contains the keyword ID.
    • Work Around- Use the Customization Manager to change the Users (i.e. default any ID fields to User ID) and then add a custom field (i.e. ActivityInfo1) on the Activity Form and then change the name. This allows you to add any fields you did not want to adapt to the default (i.e. Bib. ID)
  3. If you rename Activity Reference Name you must also rename Reference Name so that the field will be correctly labeled on all forms and grids. This is because the ReferenceName field is being aliased as ActivityReferenceName for certain queries.

Renaming Aeon Client Fields

To customize a field's description:

  1. In the Template Name field, select the template that you want to use with the field customization.
  2. In the Field Name field, enter thefieldnamethat you want to customize.
  3. In the Display Name field, enter the name that you want to display for this field in client grids and forms.
  4. When you are finished customizing fieldnames, save your entries by clicking the Save button on the Field Customizations ribbon.

Hiding Aeon Client Fields

To customize field visibility:

  1. In the Template Name field, select the template that you want to use with the field customization.
  2. In the Field Name field, enter thefieldnamethat you want to hide.
  3. In the Hidden field, check the checkbox to hide this field in all client grids and forms.
  4. When you are finished customizing fieldnames, save your entries by clicking the Save button on the Field Customizations ribbon.

Note that visibility, as set in the Field Customizations table, supersedes any existing template settings. Hidden fields and grid columns cannot be re-added from within the client. See the section titled

Understanding the Hierarchy of Form and Grid Settings under Creating and Assigning Templates to Staff Users.

If the staff client has debug logging enabled from the Client Options, any grids that are displayed will log the names of custom fields. If a grid has a field that does not match the underlying table field names, that grid field name will be noted in the log and can be renamed or hidden via FieldCustomizations.

For example, Signed in Users on the Main form has a field called Name that is a combination of LastName, FirstName, and Username from the Users table. To find the field name to rename it, debug logging will note all those grid field names.

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback