Adding New Fields


OpenGround Cloud Professional comes with a great number of tables and fields that should meet the demand of the majority of users. However, further tables and fields may need to be added to allow for further data to be entered when needed.

Before you start

  1. Review your data model and check if fields already exist that may or altered for use. This is to avoid unessesarily creating duplicate fields.
  2. If a new field is required, decide if it will be utilised accross all projects (saved at system level configuration) or is bespoke to a specific project (saved at project level configuration), you will need to discuss this with your OpenGround Configuration Manager for preferred approach. 

Creating fields within System Level Configuration

Whilt in the system level, to add a new field, first access the "Configuration Packs" and then the "Manage Model" button after selecting the config you want to edit as shown below. 

The Model Structure window will then appear listing all of the available tables. Select the table that is to have the new field added and select the "edit" button.  

The Edit window will then appear listing all of the currently available fields within the selected table. To add a new field, select the "Add header" button at the bottom of the window.

The Add Heading window will then appear allowing for the definition of the new field to be added. All of the fields will need to be entered to allow for the field to be stored correctly. Any values that do not match the required validation will appear as a warning, allowing for any details to be corrected.

Below is an example of Creating a "TEST" header within the "LocationDetails" Group.

Once all of the values have been entered, select the Save button and the field will then appear in the user interface within the Grid. 

"Manage Grid" allows you to add/remove and reorder fields aswell as creating completely new grids to be used within a project. 

 

 

Creating fields within Project Level Configuration

The steps are the same as above, but you will first need to access the project of interest before entering into the configuration pack.

 

Other notes