Affects

Description

Details

Reference

Konect Manager can now import records from GIS files into datasets based on the value of a user specified unique ID field.

Konect manager will now produce a log file for all imports.

Previously the appending and updating of records in datasets by importing a GIS file was based entirely on the value of the konect system field '_id'.

This release allows the user to select any field within a dataset to be used for selecting records for updating and appending. The selected field should be one that contains unique values. The konect system field '_id' can still be used if it exists in the import file. 

Please note: if an external id field is chosen any records without a value for the field will be skipped during the import.

A log file of the import is generated in the folder

C:\Users\<user_name>\AppData\Roaming\Global GBM\Konect\Konect Manager

where <user_name> is the name of the user.

The format of the name of the log file is 'IMPORTLOG_<dataset>.<extension of import file> where <dataset> is the name of the affected dataset and <extension of import file> is the same extension as the import file. For example, if the MapInfo file 'TEST_DATA.TAB' is imported into a dataset called 'MyDataSet', the log file will be 'IMPORTLOG_MyDataSet.TAB'.

The log file has extra columns/fields added to it which detail how each imported record was processed.

Affects

Description

Details

Reference

The 64 bit version of MapInfo Pro V15.2 introduced the Extended TAB file format that allows the creation and editing of TAB files greater than 2 Gbytes in size.

The new type of TAB file is recognised by the text 'Type NATIVEX' in the .TAB file.

Konect Manager does not support this new NATIVEX format and any attempts to import a NATIVEX TAB file will fail.

Note that MapInfo Pro V15.2 (64 bit) and later can save a NATIVEX TAB file in the old format provided it is less than 2 GBytes in size. Thus if a NATIVEX TAB file needs to be read into Konect, use MapInfo Pro to first save the file to the old format and then import the old format file.

1. Unique values in list items can no longer be directly edited. If the unique value in a list item needs to be changed, then delete the list item and add a new list item with the required unique value. NOTE: Deleting and then adding a list item in a parent list will result in loss of data in related child and descendant lists, i.e. grandchildren and great-grandchildren lists. When an item is deleted and then added in a parent list, all its descendants should be re-imported.
2. New list items can now be added to a parent list without destroying parent-child list integrity. When a list item is added to a parent list, each child list of the parent list will be given a new entry which consists of the default value for the child list and whose parent item value is the unique value of the new item added to the parent list.
3. List items can now be deleted from a parent list without destroying parent-child list integrity. All its child lists and grandchild lists etc. are now automatically updated.
4. The purpose of the changes in Items (2) and (3) is to allow existing parent-child lists to be updated without losing the association between lists and their list fields in a form. Previously, any edit to a parent list required the deletion and subsequent re-importation of the parent list and all its descendants. This resulted in the form list fields being disabled, requiring re-association of the lists in the form following re-import of the lists. Now the user can either add a new list item to or delete a list item from a parent list and then re-import the edited child list from a CSV file without losing the association between the lists and their list fields in a form.