---
title: "Release Notes"
canonical: "https://servicedesk.maxgeo.com/space/LogChief/1273233410/Release%20Notes"
format: markdown
---
Build 3.3.0
| | | |
| --- | --- | --- |
| **Feature/Bug Fix** | **Component** | **Description** |
| Feature | Data logging using Database-View | From LogChief 3.3, user can use “mapping with database-view” to synchronise and import data. Before this version, they were using “Sync specific mapping or mapping without database-view” to perform synchronization and import operations hence no need to create dummy mappings |
| Feature | New Licensing Process | LogChief licenses are no longer hosted and activated using CopyMinder. From version 3.3.0 and upwards, all LogChief and MxApp licences will be hosted by maxgeo, with all API communication (activation) made over secure HTTPS. A new Licence key will be required for each installation, and requesting a new or updating an existing licence is now much easier. See the Installation Guide for more information. |
| Feature | Geometry Data-type Support | |
| Feature | Time Data-type Support | |
| Feature | Profile Filter | During Profile creation, or in editing the profile, LogChief will allow a user to create/update Profile filters. LogChief will apply this filter to a Profile and a user will only see the relevant filtered data.
E.g. If you add Profile-Filter HoleType = ‘DD’, Profile will only display HoleIDs who’s Hole-Type is DD. |
| Feature | GUI to map columns for Distribute Planned Collar functionality | Added a mapping screen for the user to map the columns for tblDHColl & tblDHSurv against tblDHCollPlanned table. LogChief will allow a user-determined mapping to distribute data from tblDHCollPlanned table to tblDHColl & tblDHSurv. |
| Feature | Copying values for fields with similar names from DHSample to DHSampleQC | Assigning a Duplicate for a Sample will copy all the fields (Sample_Type, Sample_Method, Sampled_By, Date_Sampled) into the SampQC table, rather than just the Hole_Id, Depth_From & Depth_To |
| Feature | Deleting QC data when deleting Samples | LogChief will delete QC data associated with a deleted Sample |
| Feature | Update/Delete Standards as per HoleID | If the SourceID field is mapped for Standard-Sample, LogChief will use the SourceID field to store the HoleID and use it for Update/Delete operations when a user performs these operations from a Collar Logging View. |
| Feature | LogChief Interface Enhancements | maxgeo has made a few changes to the menu items on the Main-Screen and Logging-Screen. This will help to speed up data logging as well as other operations. Please refer to the User Guide or Help file to know more about these changes. To allow for smaller screens and more space for customer headers, some of the tools have been grouped in the bottom ribbon of the logging interface and sync tool buttons have been consolidated to a pull-down menu in the home screen. |
| Feature | Export and Import for Visual Checker | A Visual Checker definition will go along with Profiles during the Configuration export and available for import during the Configuration import process |
| Feature | Priority field consideration for Interval Overlap functionality - Relogging | “Interval Overlap check” will also consider the “Priority” field if an administrator maps it during the configuration process. This will allow a user to re-log same intervals with different priority values. |
| Feature | Option to enable/disable triggers during Import Data & Refresh Library operations | This will help to bring in any dependent data which are inserted by triggers e.g. bringing in data for tblSampleRegister while importing samples in tblDHSamp table. Disabling triggers, a user can now get the data into LogChief and fix it there. Please note that this may result in a failing import operation as enabled triggers may cause errors. |
| Feature | Added an option to go to Logging-window directly | Upon selecting this option, a user will be directed to the Logging-Window when they run LogChief for the first time. The user can return to the home screen by clicking the home button on the top right-hand side of the logging window |
| Feature | Added an option to highlight first or last row of the Logging Grid | User has an option to choose which row they want to highlight when they switch tabs in the logging views. This functionality will be applicable on downhole and child table-types |
| Feature | LogChief will support date fields with a default value in a multiple table logging-view | LogChief will only consider the date portion for this situation, time portion of the default value will be discarded |
| Feature | Other Enhancements | - Reset "Allow Null" as per database for existing Configuration i.e. during edit configuration process, LogChief will recheck “Allow Null” status for each field and update it
- Added Active-Flag for the Configuration. This will help other MxApps to find out the current configuration during multiple configuration scenarios
- During Library setup process, on Configuration Wizard, a user can search for a library table by typing the part of the name of the library table. This will be very helpful in the database-view
- User can copy-paste filters during Synchronisation operation
- Added new icons for Profile
- LogChief supports library table in updatable-database-view’s definition. Now user can add a database-view to themapping during configuration process
- Contactinformationandbrandingareupdated.Installationdocumentationalsoupdated. |
| Known Issues | Layout designer | Enhancement to add a save button in layout designer. |
| Known Issues | Error handling for exceeding field length is not logical.
LogChiefneedstocapturetheseerrors in a more user-friendlymanner | Error when field length is exceeded for Comments Field: 'An error has occurred please check the log for details.' Error when field length is exceeded for a numeric field: 'Arithmetic overflow error converting numeric to data type numeric.' |
| Known Issues | Multiple rows, predefined holes and samples | Multiple rows should refer to the Pre-defined Hole IDs and Sample IDs lists. Currently, the two tools for ID creation do not communicate. This would be an enhancement if the tools carried the same entered information and less repetition for the user. |
| Known Issues | System displays Out Of Memory Exception when entering 1000 | ISSUE: Using the Multiple Row feature in LogChief 3.2 the user logging Multiple Hole has issues recording 1000 Parent Hole IDs and Child values. Limitation is under investigation. Best practice is that a user should only log what will be immediately logged and synchronised with the Database; otherwise, operations will be slow.
STEPS:
1. Open LogChief 3.2
2. Select Workflows > a Logging Profile > then a Collar Group
3. Select the Multiple Row feature from ribbon and enter Details for 1000 holes
UNEXPECTED OUTCOME:
1. System does not crash but gracefully stops with an endless loop on the screen
2. This occurs also for 400, 300, 200 & 100 holes. No error message looks to internally time out.
3. If user selects escape and reopens LogChief - Collars are recorded but no child values
EXPECTED OUTCOME:
1. LogChief3.2 shouldbeabletocreate 400-500holestosimulateaGradeControlscenario |
| Known Issues | LogChief installer installs tools and MX Apps with LogChief | Add options to install other applications with LogChief. If none are selected, none will be installed. This gives the client/administrator control over what can and cannot be installed and seen by a user |
Build 3.2.4 and below