Well Seeker Pro Import Function Update
Last updated
Was this helpful?
Last updated
Was this helpful?
With the release of Well Seeker Pro version 2.1.0.33, the Well Seeker / Compass Import Settings dialog has been removed. The options in this dialog have been replaced with an internal logic process handled automatically by the software when dealing with Well Seeker Pro export files and remote data fetch events. This technical note details the change and the reasoning behind it. Note, the Compass import settings changed in a previous revision, details of which can be found in the following document:
When importing a Well Seeker Pro export file, Well Seeker needs to know how to handle data associated with items in the database that also exists in the export file being imported. Historically this was handled using the user definable options in the Well Seeker / Compass Import Settings dialog. This gave the user control over what data they wanted to be overwritten, never overwritten, or given a prompt to decide on a case-by-case basis. However, this process had the following downsides:
The process / options were poorly understood by a significant number of users.
Due to this, databases were frequently erroneously filled with multiple copies of database tree levels, with slightly different naming e.g.Field-1, Field-1 (2) etc.
The options for this process were saved in the setup file for each PC, so the import behaviour would vary on a PC-by-PC basis within an organization.
If the user had Ask selected as the import setting, large imports could result in a time consuming process.
To streamline and simplify the process, a new import feature has been implemented.
In the new import process, the user is given two options, that will determine how the Well Seeker Pro export file is imported.
Import: All export file data will be imported, including all reporting data.
Import – No Reporting: Only database tree items and associated properties are imported. All data associated with Well Seeker Pro’s Reporting module is excluded from the import. This will allow users to pull in trajectory data, such as plan updates from the office, without concern about overwriting reporting data.
In all standard cases where a name match is found between the export file and the database, the outcome is the database data is overwritten with the data from the export file. The only exception to this is when a duplicate level scenario is encountered under a different parent item in the database tree.
The benefit of this new method is that it only gives the user two possible options, duplicates are never created, it is fast and there is consistency across the company when importing Well Seeker export files.
The way in which duplicate child items, under different parent items in the database tree are handled has also been updated. The logic is described below:
The tables below show examples of a simple Well Seeker export file imported into Well Seeker Pro using the new process, including a scenario where duplicate level items are dealt with:
Export and Database naming matches
Export and Database naming mismatch, resulting in duplicate level resolution logic
A message dialog appears after the import process has completed, informing the user if any duplicate level items have been resolved.
An importFileLog.txt file is also created in the debug folder. This contains the same information that is displayed in the message dialog above, and provides a reference for the user once the dialog has been closed. The debug folder file path is: C:\Users\USERNAME\AppData\Roaming\Well Seeker Pro\Debug.
It is now very clear to the user where duplicate issues are occurring and at what level. It is also extremely easy to delete any unwanted duplicate data, as it is all kept together under the level that had the naming mismatch.