---
title: "Profiles"
canonical: "https://servicedesk.maxgeo.com/space/LogChief/1276051465/Profiles"
format: markdown
---
> Macro (toc)
After setting up a Configuration (which defines the Logging database structure), create a Logging Profile(s) to define how data will be logged to the Logging database.
Logging Profiles include:
- Definitions of Logging Views (grids) and Custom Layouts;
- Customisation of Logging Schema (Required fields, defaults, validation, calculation rules and cell formatting);
- Library Table filtering;
- Library Favourites (ranking);
- Logging View display settings (column aliases, widths, visibility);
- QC Policies;
**Opening an existing Profile**
Profile directly depends on Configuration. So user needs to make sure that desired configuration is selected, if not, please [open the Configuration ](#page38)and then select the profile.
The selected Configuration will look like image below.
Click the Workflow that the Profile belongs to, then in the next pane to the right, click the profile you wish to work with.
*Note: Use the mouse to hover over the Profile icons to view their names.*
### **New Profile**
To create a new Logging Profile, click on the *Logging Profiles > New* menu item through the icon in the main window of LogChief to load the Logging Profile Wizard.
#### **Profile Name**
Select the Configuration mapping for which the new profile should be created. Note that any logging
Profile can only be associated with one Mapping. Enter a name for the Profile, select a workflow the Profile is to be associated to, and select an icon to represent this Profile.
*Note: The Profile name must be unique to the Configuration it is associated with.*
#### **Profile Layout**
LogChief allows the user to customize the logging interface through the use of groups, views and custom layouts.
**Add Group**
To add a group, click on the Add Group button and enter a name for the group.
**Remove Group**
To remove a group, right click on the group to remove and select Remove Group from the context menu.
**Add / Remove Views**
After creating a Group, create a View under the Group. A View in LogChief represents a form that you log data to.
Each View you create will be associated with columns in the Configuration Database. A View can contain columns from more than 1 table in the configuration database. We call them merged Logging Views. There are some rules to merge two or more tables in single LoggingView, they are:
1. Cannot merge tables from Parent & Child Table-Types
2. Table have to be from same Table-Types
3. If not from same TableTypes, following combinations are possible:
- Downwhole with DownholeSample
- Downhole with DownholeSmapleQC
- DownholeSample with DownholeSampleQC
- Child with Child
There are some limitations when user uses Database View to create a Logging View, they are:
1. Cannot be used in merged Logging View, not even if they follow above mentioned criteria.
2. All columns will be added to Logging View, a user can use the View Setting to hide them if they do not want to log data against the columns.
3. The Logging Group(s) you create will be displayed on the main LogChief screen as seen below on the right hand side.
**Interval Properties**
On Layout window, If you right click on the Logging View name, apart from Group and View options, you will see the "Interval Properties..." option. This option is enabled for all Logging Views which has **"Depth From"** and **"Depth To"** columns mapped.
**Default Interval**
This option sets the default value for the intervals. E.g If the default vlaue is 5, the value of "Depth From" and "Depth To" will be set every time when a user clicks on a new row and the difference will be 5.
**Prevent Interval Overlaps**
When ticked, will warn you if you enter overlapping intervals. This will stop LogChief to save the data into the database table. When user enters overlapping intervals, LogChief throws an error and ask user to correct this erroneous value.
From LogChief 3.2, it will also consider "Priority" field. So, if you want to re-log intervals you can use different priority values and log same intervals. To make this happen, you need to set Priority field in Required field mappings, during the Configuration process. Priority field is available for Downhole & DownholeSample table-types.
Note - There is a trigger in each downhole database tables which prevent "Interval Overlaps", please make sure you are not using both the options at same time. This will result a system overhead
**Warn Of Interval Gaps**
Give visual indication to the user about a gap in the interval.
#### **Custom Layout**
Custom Layouts provide an alternative way to log data; the default way being entering data into a grid format. This Custom Layout designer allows users to creating a logging form using common windows controls. The main feature of Custom Layouts is the ability to arrange/layout each field value as desired.
To navigate to this Custom Layout designer, click on a view previously created on the 'Profile Layout' screen. Be sure it has columns assigned to it then click the 'Layout' button.
**Data Source** window shows all the columns available for the Logging View. It shows in four colour codes as **Red, Orange, Yellow and White**.
| | |
| --- | --- |
| RED | They are Required fields and user must include all required fields in the Grid on the Form or directly on the Form if Grid is not added |
| ORANGE | They are Required fields with default value; User must include them in the Grid on the Form or directly on the Form if Grid is not added if it is a joined Logging View |
| YELLOW | They the fields with default values; User must include them in the Grid on the Form or directly on the Form if Grid is not added if it is a joined Logging View |
| WHITE | Are the rest of the fields; User can include them if they want to log data against |
Header fields will never come in **Data Source** window as they should not exist at the Form.
Below is an example of a Lithology Data View where a 'Text box' is used as the input for Depth From and other fields. A combo box used for Lith1 Code. Combo boxes are used for fields linked to an associated Library table and appear as a dropdown lists while logging in LogChief.
**Add Field**
There are two ways to add fields to the custom layout:
1. Drag a field from the Data Source panel onto the custom layout canvas
2. Drag a control from the Toolbox panel onto the custom layout canvas and then drag a field from the Data Source panel onto the control
Grid Control on the Custom Layout is only used to navigate through the records on Custom Layout. It is the good practice that the user should only include the necessary fields on the Grid Control. Do not repeat the fields on the Grid Control which are already on the form as this increases the system overhead.
Column order and visibility of the columns on the Grid Control depend on settings on the [View](#page62) [Settings ](#page62)screen. So don't worry about adding columns in the right order or too many column in the
Grid Control. In case of a joined logging view, just add the columns and set their **order** or **visibility** on View Settings screen.
**Remove Field**
To remove a field from the custom layout, click on the field's control in the custom layout and click the Delete button in the toolbar.
**Text Box - Extra Settings**
There are some additional settings in the Text Box control which can help you to present data in better ways. When you drag a field onto the form, LogChief will set these properties based on the field's datatype.
1. Num - Is Numeric: Data displayed is Numeric or Not
2. Num - No. of Decimal Places: How many decimal places text box should display
3. Max Length: Maximum length of the data displayed. This will include decimal point
4. Using ReadOnly settings, you can stop a user from entering the value (For a calculated field)
If you want to use multiple lines text box, use a RichTextBox control E.g. Comment Box in image above.
**Date Control**
It is very important to note that whenever you use a Date Control on the form, it must be used with a Group Box (i.e. it has to be put under the Group Box). Please check the screenshot above.
**CheckBox Control**
CheckBox does not support multiple lines. To display multiple lines with CheckBox Control, use it with Label Control.
When placing a CheckBox control on the form, it will look like a simple CheckBox control but when used on a Logging Screen, the CheckBox will be changed to a "Yes/No" sliding button. Please see the images below.
During the form design:
During Data Logging:
Note: The minimum size for the CheckBox control has to be 32 X 64.
**PictureBox Control**
This control will be used to show the picture on a Form Logging. The User needs to add this control on a form and map a field which is used to save "Path of Photo" or the actual "Photo".
A User must add the field "dbo_tblDHPhoto_Path" in **Grid** on Custom Form otherwise it will be difficult to add the data for the **PicureBox** control.
This control works with ["Field Photo" ](#page25)button and "[Browse File](#page119)" button, highlighted in image above as "1" and "2". These buttons will help the user to select a Photo.
From LogChief Release 3.1.6, we have enhanced few existing functionalities to help users save design time. For example:
- Property changes applicable to all selected controls. E.g. If you select 5 controls and change font size, LogChief will change font size for 5 selected controls.
- Removing fields from the grid if they don’t belongs to the table. After this change, we do not need to remove the grid and add it again if we are upgrading the Configuration or copying the Layout from other Logging View.
- When you drop a database field on the form, the controls will be placed side-by-side.
- For Label control, Auto-Size property will be set to true.
#### **Edit Schema**
The Schema page of the Logging Profile Wizard allows the user to adjust the properties of the Logging View Fields. These settings will be reflected directly on the Logging form.
**Required**
If checked, the column header for that field will be Red on the logging form.
**Default**
Define a default value for the logging field. When a new record is generated for the View, the Fields value will automatically be set to this default value.
Note: The value can still be modified while logging.
**Validation Rule**
Define validation rules for a field. The value entered for this field on the Logging form must satisfy the defined validation rule, data will be saved in the database however LogChief will continue showing "X" mark for failed validation.
To build a validation rule, click on the Validation Rule cell for the field you want to add a rule to and then click on the '...' button within the cell to launch the Validation Rule Builder. In the example below, a rule has been set on the column [tblDHColl].Local_East. It prevents the user from logging data into the column with a value outside the range '300000' and '300100'.
**Calculation Rule**
Define calculation rules for a field. The field assigned a calculation rule is assigned the result of evaluating the rule during logging.
To build a calculation rule, click on the Calculation Rule cell for the field you want to add a rule to and then click on the '...' button within the cell to launch the Calculation Rule Builder. In the example below, we've set a calculation rule to automatically subtract '100' from the [tblDHColl].Max_Depth field when the user enters a value on the Logging form.
**Format Cell**
Define Visual checking rules for any field.
While logging data into the Logging form, you can format the cell colors based on the cells value. In the example below, we've set a condition on tblDHColl.Max_Depth field. On the logging grid or form, cells belonging to this column will have a white text & red back colour whenever the value is > 200. (This is meant to highlight all the tblDHColl records with a depth greater than 200m).
Screen below shows available Visual checks.
To add a new validation, click on "Add" button and following screen appears.
Create the expression and select "Fore Colour" & "Back Colour".
By default, Visual checks are disabled, to make them enable please check the Option 1 - Logging [Window Setup ](#page188)link.
#### **Library Tables**
In the Configuration Wizard ['Library Tables' ](#page33)screen, we specify the foreign key tables and fields to select. This screen helps refine the earlier selection.
The Library Tables page of the Logging Profile Wizard allows the user to adjust the properties of the Library Tables (lookups).
**Filter**
Filter the library values for any field with a lookup.
To filter the library values for a field, click on the Filter cell and then click on the '...' button within the cell to launch the Filter Builder.
By default, columns mapped as Code and Description are selected. A User can change the selection and save the profile.
For the example above, for dbo_tblDHColl_Orig_Grid_ID, CoordinateSystemCode, DatumCode, Description, ProjectionCode, SourceRef columns will be displayed on Logging Screen.
User can make changes here. E.g. In the below image, a user can hide the Projection and SourceRef columns and increased the size of dropdown.
**User's preference will overtake the default Profile settings.**
**Profile Filter**
When ticked, LogChief will use this Library filter to filter whole Profile. This option is only available for Parent Table Types i.e. Collar, Parent & Point Sample.
E.g. If user ticks Hole Type to act as Profile Filter and set a Filter "Code = 'AC'" for Hole Type, LogChief will only show the data related to Hole Type = 'AC' for all the logging-views in the Profile. Same rules is applied to newly logged data.
If we check the Logging Screen, it will only shows the Holes which satisfy Profile Filter
Close the logging screen and select other profile, one which doesn't have Profile filter, and open the
logging screen
As seen above, in this logging screen, we see all the Holes.
#### **Library Favorites**
This screen follows on from 'Library Tables' allowing users to further customize the linked foreign key fields. Here they specify the order which foreign key values will appear on the dropdown box on the Logging form.
To rank the library values for a field, click on the field in the left panel and then assign a ranking number to the values you want to appear at the top of the dropdown list.
#### **View Settings**
Set the display properties of the Grid Control on Logging Views as well as Grid Control on Custom Layouts. The same setting will be applied to both Grid Controls.
**Alias**
Alias set here will be displayed as the header for Grid columns. It will also appear in the header on Logging Form.
**Visible**
Set whether or not this field is visible in the Grid Control.
**Copy**
Set whether or not values from this field are copied when using the Copy Record feature while logging data.
**Width**
Set the default width of the grid column for this field. (length in pixels).
**Order**
Set the order of the columns using the Up and Down buttons. Columns will appear in same order on
Grid Control on the Logging View or Custom Layouts. It is a good practice to make sure that:
- All Headers columns are in the right order and always appears on the top. (You will never see the Headers Columns but this is good for processing).
- Hierarchical column are set in the right order otherwise they will not function properly.
#### **QC Policies**
LogChief provides functionality to record QC policies for data samples. This screen below is where you would define those rules.
Adding a Sample record, you select whether it is a Downhole or Surface Sample, followed by the type of sample: Duplicate, Standard or Blank.
For Duplicate QC policies, the Sample record will be copied from the Sample table and inserted into the 'Downhole Sample' table. The duplicate is to simulate two of the same samples being sent to the laboratory.
For Standard and Blank QC policies, the Sample record is removed from the Sample table and inserted into the 'Standard Sample' table. This is to simulate 1 in every Xth sample sent to the laboratory being a 'controlled' sample (a sample with its assay values exactly known).th
In the below example, a 'Duplicate' record is created in the 'DH Sample QC' table every 10 record.th
A 'Sample' record is also created in the 'Standard Sample' table every 8 record.
**Add QC Policy**
To add a policy, select a sample type, type, option, frequency, offset and default value in the new record row in the grid.
- Sample Type: apply to downhole samples, surface samples or both
- Type: Duplicate, Standard or Blank
- Option:
- Sample count - create a QC sample every x samples
- Sample suffix - create a QC sample when logged sample ends with x character/s
- Frequency: create QC sample ever x samples or when x appears at the end of the sample ID's suffix
- Offset: start counting after x samples
- Select Standard: a dialog will appear, every time a standard is automatically created, allowing the user to select a standard type
- Default Value: populate qc category field with this value
**Remove QC Policy**
To remove a policy, click on the policy to remove and click the Remove button.
**Summary**
The summary displays all the settings defined in the Logging Profile for the user to review.
**Update logging database**
Re-create the logging database with the latest schema changes.
**Clear logging data from the logging database for this profile**
Clear all logged data for this logging profile. This will also re-import all the library values from the main database.
**Save...**
Click the Save button to save the summary as a rich text file (rtf).
**Print**
Click the Print button the print the summary.
**Save**
Proceed with the Logging Profiles changes (and save the settings).
**Cancel**
Cancel all changes made to the Logging Profile. The Profile settings will be reverted to the state it was in before the current Profile editing started.
### **Edit Profile**
To edit any Profile, click on the * > Logging Profiles > Edit* menu item in the main window of LogChief.
This will open the Logging Profile Wizard.
In the first screen below, select the profile you wish to edit from the Dropdown (contains a list of all current profiles in the Configuration, ordered by workflow). You have the option here to modify the icon, changing workflow or continue to the Profile editor by clicking 'Next >'.
The following sections of the Wizard, where any modifications are made, follow the same window progression and setup as when creating a new Profile. For a detailed explanation of each step of the process please navigate to [Profile Layout ](#page43)under the [New Profile ](#page42)topic.
### **Delete Profile**
To delete a Logging Profile, click on the * > Logging Profiles > Delete* menu item in the main window of LogChief.
Select the Logging Profile to delete and click Ok.
### **Duplicate Profile**
To duplicate a Logging Profile, click on the * > Logging Profiles > Duplicate* menu item in the main window of LogChief.
The dropdown will display all profiles user has access to.
Select the profile you want to duplicate and give it a new name. LogChief will duplicate the profile with new name.
### **Enable All**
To enables all Logging Profiles on single click, click on the * > Logging Profiles > Enable All *menu item in the main window of LogChief.
This menu option will allow you to enable all available profiles in the selected configuration. This is very helpful if you have several profiles and you have edited the configuration. It has a few limitations though. E.g. It only enables the profile and does not consider big changes like library changes or required field changes. If you have made any changes related to library or required fields, please edit the profile manually.