DataPort Release Notes
Current version: 3.5.5 - Released 2012.2.27
Known Issues:
- Modification to DEP (Data Execution Protection)
settings may be required
(see <CGStartupError.htm> file located in program folder)
Version 3.5.5 - Released: 2012.4.27
- <Bugfix> - Corrected an error incurred
importing CSV text files under certain conditions involving field
qualifier characters and multi-line fields (introduced in build 2.4.5)
- <Bugfix> - Bypassed invalid Global
Distribution Entries in GAL instead of incurring hard failure
- <Bugfix> - Corrected <Updates> from
occurring when "Add New Only" option selected
Version 3.5.4 - Released: 2012.4.10
- <Bugfix> - Corrected "thousands" and
"decimal" separator issue for numeric fields selected as "update" key
fields for non North American regional settings
- <Bugfix> - Corrected issue resulting from
entering a blank custom export field name
- <Bugfix> - Corrected gender field update
issue
- <Bugfix> - Corrected error caused when
attempting to drag a map field outside of field map list
- <Bugfix> - Corrected extraneous message
indicating missing <key fields>
- <Bugfix> - Corrected template error when
Outlook folder path exceeded 255 characters
- <Bugfix> - Corrected issue when importing
text file that contained a text qualifier character inside of already
qualified field data
- <Change> Combined Template <Save> and
<SaveAs> functions
Version 3.5.3 - Released: 2012.2.22
- <Bugfix> - Corrected EmailAddress fields not
updated on "Update" import
- <Bugfix> - Corrected export of Currency
fields to Text file types
- <Bugfix> - Corrected <IgnoreMessageClass>
selection option on Export
- <Bugfix> - Corrected error when <key> field
type differs between contact folder and data source and <Del Con If No
Match> option is selected
- <Change> - Combined Template <Save>/<SaveAs>
buttons
Version 3.5.2 - Released: 2012.1.3
- <Bugfix> - fixed "otherstreetaddress"
separated lines1-4 not exporting correctly
- <Bugfix> - fixed export template recall
not exporting "streetaddresses" lines 1-4 correctly
- <Bugfix> - corrected error encountered when
running multiple text based exports back-to-back in same session
Version 3.5.1
- Released: 2011.9.30
- <Bugfix> - Corrected error when recalling a
template using Excel/ workbooks containing only one worksheet entry
- <Bugfix> - corrected issue involving
UDFs at folder level not being created when new contact items
added via an <update> import
- <Bugfix> - corrected error occurring
processing a text file continaing a row with more fields then
contained in the header row
Version 3.5.0 - Released: 2011.8.21
- <Change> - Internal component update to
minimize issues when running multiple ContactGenie programs (legacy,
current, and/or customized) ContactGenie
programs on the same system
- <Change/Bugfix> - Selection filter only
allows the <Contains> and <Not Contains> operators for Outlook keyword
fields. Using any other operator (i.e. = ) on a multi-valued keyword
field generated an error
Version 3.4.2 - Released: 2011.8.14
- <Change> - Removed Export Output DisplayAs
option (ExportName or OutlookInternal). Selecting English language
results in the same field names being exported as if OutlookInternal was selected
which resulted in an error when another regional language was selected.
- <Bugfix> - Template size for import file
name expanded to 255 characters to allow for names exceeding the
previous internal limit of 150 characters
- <Bugfix> - Corrected issue with Filter
fields not being populated with selected folder field names when
recalling an export template (any filter created was still applied but
no changes could be made to the filter)
Version 3.4.1 - Released: 2011.7.8
- <Bugfix> - Corrected error encountered
when <DelNoMatch> option selected using Selection Filter with (Is/Is
Not Null/Blank or Like operators) with non-English regional settings
Version 3.4.0 - Released: 2011.6.28
- <New> - Option added to <Update Import>
enabling contact items to be automatically deleted in contact folder
that do not exist in the input data source based on the specified
<update key fields>. Option will not be permitted if any <update
key field> is found to contain a <NULL> value in the input data source
(applicable only for Excel, Access, MS SQL file types)
- <New> - Preview option to view
differences in mapped field values between source data file and target
contact folder for <Update Import> modes. Information available in an
MS Access database file and can optionally also be saved to a CSV file
- <New> - Import statistics now
include additional elements reporting <unique> and <total>
duplicate items found in both the source data file and target
contact folder based on the <Update Key fields> specified in the
field map
- <Change> - Updates to contact items
only applied if one or more mapped fields have a difference
between the source file and contact folder otherwise leaving the
LastModificationTime unchanged
- <Bugfix> - Corrected issue not allowing
export file name to be changed when the contact folder resulted in an
initial invalid file name (i.e. contained a "/" in as part of the
folder name)
- <Bugfix> - Corrected issue related to
Exchange environments such as Hosted accounts where no AddressBook
existed (i.e. <All Users>, <All Contacts> or <All Groups>). Can now
enter an AB name of <N/A> bypassing future AB checks.
- <Bugfix> - Corrected mapped
field names to correctly utilize <Display As> value in field map
for language specified instead of Internal Outlook names
- <Bugfix> - Corrected issue where a
mapped field would incorrectly show as an <Update Key Field> when
using <drag 'n drop> from within the Field Map list.
Version 3.3.5 - Released: 2011.4.28
- <Change> - Internal component maintenance
updates
- <Bugfix> - Corrected minor UI issues
related to clearing field maps
- <Bugfix> - Corrected errors occuring when
using "Like" operators in filters
- <Bugfix> - Removed "Select/View Populated
Fields" buttons when exporting GAL items
- <Bugfix> - Corrected error occuring under
some conditions after repetitive changes to Field Map DisplayAs
language setting
Version 3.3.4 - Released: 2011.3.27
- <Bugfix/Changes> - Various changes to
correct error messages caused by changes to current Outlook
environment after a template was saved and then subsequently recalled (i.e. missing user-defined
fields due to custom form changes)
- <Bugfix> - Fixed "Drag 'n Drop" to enable
re-sequencing of output fields on export and corrected <drag 'n drop>
error under certain conditions when moving field names in the field
map list
- <Bugfix/Change> - Display warning
message regarding GAL <User/Contact/Group> AddressList folder names if
GAL folder cannot be found as defined in DataPort default settings.
Error caused by missing GAL folder names replaced with information
messages.
Version 3.3.3 - Released: 2011.3.17
- <Bugfix> - Corrected issue with null value birthday/anniversary fields
Version 3.3.2 - Released: 2011.1.30
- <Bugfix> - Gender field checked for for first
character capitalization on values
- <Bugfix> - Corrected error gnerated when contact
folder contained a <.> (period)
- <Change> - Empty rows/records in MS Excel/
Access/MSSQL data sources skipped on import
Version 3.3.1 - Released: 2011.1.6
- <Change> - <Populated Field> information no
longer retrieved by default when contact folder initially selected
reducing potentially significant startup delays when a very large contact folderis
selected particularly with large numbers of user-defined fields.
- <Change> - Check for MAPI individual field
errors no longer done <by default> of all fields when folder selected
reducing startup delays particularly for large contact folders with
large numbers of user-defined fields. Mapi Error check now only done
on <mapped> fields if a MAPI Error has been encountered when
attempting to read contact data (more info in help file)
- <Change> - Export field size max for Excel
fields limited to 32000 characters (Excel cell size max)
- <Change> - Export field size max for MS
Access fields limited to 65000 characters (Access memo field max)
- <Bugfix> - Corrected issue when using
<BillingInformation> field
Version 3.3.0 - Released: 2010.12.22
- <New> - DataPort Standard / Advanced editions
combined. CDP Adv Ed becomes DataPort 3 (excluding capability to
import from an Outlook contact folder). Refer to product page for full
details. Registered owners of CDP Adv Ed will recieve free upgrade to
ContactGenie MutliPort.
- <Change> - Export text types for MS Access
tables defined as Text(255) instead of <memo> if the source length
less than 255 characters - will dynamically change to <memo> if any
contact item contains a text length > 255 characters for a text based
field
- <Bugfix> - Corrected potential error
occuring when assigning filter criteria
Version 3.2.7 - Released: 2010.10.29
- <Bugfix> - Corrected issues where under
some circumstances UDF fields were not being updated when importing
using <Add Only> Allow All mode
- <Bugfix/Change> - Corrected error occuring
when selecting fields from a <text file> as <Update Key> fields that
were not properly initialized (Boolean, Numeric etc). Empty fields
initialized to False for Boolean, zero for numerics and zero for
Gender (= unspecified).
- <Change> - Gender field set to numeric
equivalent if field contains <F> <female> <M> or <Male> - non-English
alphabetic gender values set to 0 = unspecified
- <Change> - Can no longer select every
mapped field as an <Update Key> field and a warning message will be
displayed if more than 5 <Update Key> fields are selected
- <Change> - Updated Error Handling system
Version 3.2.6 - Released: 2010.10.11
- <Bugfix> - Corrected processing of non-CSV multi-line text files
- <Bugfix> - Corrected suffix parsing error when [FullName] field
specifically mapped on import where either [FullName] value only contained a single word name
or lastname starting with the letter [I]
Version 3.2.5 - Released: 2010.10.7
- <Bugfix> - Change made to prevent a hard error occuring
if the very rare case that a DataPort component related to Profile information retrieval is not correctly
registered or becomes unregistered/corrupted afterwards. Operation in this case becomes
restricted to the current default Outlook profile in effect. This update is not necessary
if no issues have been encountered related to profile information retrieval.
Version 3.2.4 - Released: 2010.9.19
- <Bugfix> - Corrected problem with
<Title> field not updating
- <Bugfix> - Corrected problem with
<Body/Notes> field not appending correctly in all cases on updates
Version 3.2.3 - Released: 2010.9.13
- <Change> - Updated CG error reporting system
- <Bugfix> - Corrected error reading CSV file on import
Version 3.2.2 - Released: 2010.9.10
- <Bugfix> - Corrected potential error when
using "SaveAs" for an import template
Version 3.2.1a - Released: 2010.8.24
- <Change/Bugfix> - Internal e-mail SMTP server option
removed when running under Windows 7. Outlook required to
send any internal messages.
Version 3.2.1 - Released: 2010.8.23
- <New> - Unicode text files supported on
import (Unicode character set must be the same as that set in Regional
settings (future update will allow conversion between different
character sets)
- <New> - Excel file format supported for
export
- <Change> - With the addition of MS Excel
to the export output formats, CSV files created by CDP will always
use a comma as the delimitor. CSV saved by MS Excel in regions where
the list separator character is something other than a comma, the
input data file muse be imported as a <custom delimited> file with
the delimitor character set to the regions list separator character.
- <New> - Two new "Add Only" options (<Ignore
Dupes> & <Delete Dupes>
- <Change> - Tab delimited text file
processing enhanced to deal with tab-delimited multi-line field
files created by Outlook that are not properly processed by MS Excel
or Access
- <Change/Bugfix> - Processing method
changed to bypass/eliminate random "Outlook has encountered a problem
and needs to close" message when retrieving contact items using custom
forms on some systems
- <Change/Bugfix> - Enhanced processing to
remove extraneous fields added by Outlook to the Contact item
UserProperties collection during custom form design
- <Change> - FullName standardization
function removed as an option
- <Change> - CG error handling system
expanded to handle more obscure error conditions
Version 3.1.6 - Released: 2010.7.20
- <Bugfix> - Corrected error occuring when
non-English field names selected for export
- <Change> - CSV default field delimitor set to
regional list separator character to conform to MS Office. When same
CSV file is used with a different regional setting, it becomes a
custom-delimited file
- <Change> - Field map uses user setting
default character set enabling creation of based text files
- <Change> - Faster processing of
Personal/Org forms libs on startup
- <Change> - Selecting any "root" node in
Outlook field map will also automatically select/de-select all
sub-nodes
- <Change> - Contact folder names cannot
contain a period for use by QuickPort
Version 3.1.5 - Released: 2010.6.25
- <Bugfix/Changes> - Parsing algorithm
enhanced when importing <FULLNAME> field addressing name
value formats starting with <LastName, FirstName> or <LastName Suffix,
FirstName>. This also corrected an issue of an extraneous comma being
included when no initials were included in a FullName value consisting
of <LastName, FirstName.......>. FullName values consisting of
<LastName Suffix, Firstname Initials> not parsed correctly when
importing in Outlook, are parse correctly in CDP. Recognized
suffixes are restricted to <I, II, III, Jr, Jr., Sr, Sr., Esq, Esq.>
- <Change> - Changed field type
validation for Excel files which resulted in field type comparison
error occurring when the first row in a new data source had different
fields populated then the worksheet used to create a template. This
issue is specific and exclusive to Excel file data sources and only if
the different columns are populated when importing via a template.
Version 3.1.4 - Released: 2010.6.23
- <BugFix/Change> - enhanced error handling
for situations involving
- improperly constructed custom forms resulting in extraneous and
invalid fields
- Excel workbooks incorrectly named or improperly constructed -
generally involving files
received/downloaded from
certain 3rd party services or files created via 3rd party
processes
- folder
path names cannot contain a period followed by a space anywhere within
the path for
any MS Access or Excel file
- <Change> - Number of fields that be
selected/mapped for either import/export restricted to 250 for any
single task
- <Bugfix> - folder path for default files
will automatically be set to the "application path" if the windows
account name contains a period followed by a space (i.e. John A.
Smith)
- <Bugfix> - Corrected "element not found
error" when listing Outlook fields when a user-defined field contained
a period and also encountered a MAPI retrieval error
- <Change> - Number of items that can be
imported without be registered set to 100
- <Bugfix> - Corrected error resulting from a
custom form being used but not available either because
Exchange Org forms library not accessible (where applicable) or form
no longer published to any library (folder, personal or Exch Org)
Version 3.1.3 - Released: 2010.4.26
- <Bugfix> - Corrected double commas appearing in FileAs field
if "FullName" name field imported in "LastName, Firstname MiddleName format
and FileAs format set to LastName, FirstName
- <Bugfix> - eliminated error occuring when
processing Excel workbook created by external process containing
invalid underlying references in Excel file
schema
- <Bugfix> - Eliminated trailing CRLF characters when
importing less than 4 street lines
- <BugFix/Change> - Corrected issue related
to importing multi-value keyword fields. Duplicate values contained in
imported value are removed prior to updating Outlook keyword field
when import option set to "append to keyword value"
- <Change> - Ability to change general default settings
after recalling a saved template enabled
Version 3.1.2 - Released: 2010.4.19
- <Bugfix/Changes> - Enhanced processing and error handling for issues
generated by custom fields that are either invalid, duplicates, have names that are
invalid database field names, or are assigned numeric field names.
- <Change> - Addtional performance enhancements when updating a
large number of existing user-defined fields on a per contact basis
Version 3.1.1 - Released: 2010.4.11
- <Bugfix> - Corrected issue for text field imported to
Body/Notes field only imported 255 characters
- <Change> - Added additional error reporting when selecting
contact folders with invalid EntryIDs
Version 3.1.0 - Released: 2010.3.29
(all current users are advised to upgrade previous versions to this release)
- <Change> - New faster processing engine increasing
import/export speed by almost 1000% over previous versions. All Outlook data is
normalized for Null, blank and fields containing only spaces ensuring accurate
filter results.
Version 3.0.15 - Released: 2010.3.22
- <Change> - Increased number of records that can be
processed while unregistered to 250 contacts for both import/export
- <Feature> - Added ability to select contacts
with populated fields only for export
- <Change> - Changed export procedure for faster processing
times
- <Bugfix> - Corrected "Error 6 Overflow" condition when
errors encountered during Personal/Org Forms library initialization scan
- <Bugfix> - Corrected contact selection
issue for source contact folder using message class published in Org
forms library
Version 3.0.10 - Released: 2010.3.2
- <Bugfix> - Corrected error caused by single quote
character in Message Class name
- <Bugfix> - Corrected issue where some text fields not
correctly updated in Outlook '2000 environments
- <Change> - Added "Leave As Is" option to default
settings for FileAs and EmailDisplayAs fields for both Import/Export options
- <Change> - Added additional error checks for hosted
Exchange accounts
- <Change> - Removed Part fields from criteria field
selection
Version 3.0.9 - Released: 2010.2.22
- <Bugfix> - Corrected error encountered when processing
text files with no headers
- <Bugfix> - Corrected issue when processing multi-line
tab delimited text file with no text qualifier specified
- <Bugfix> - Folder "ClearAll" parameter not set correctly
when recalling a template
- <Bugfix> - Corrected error tjat could occur when changing
import mode multiple times between "Add" and "Update" multiple times
Version 3.0.8 - Released: 2010.2.17
- corrected issues involving template recall and command line processing
- <Bugfix> - Corrected errors caused when changing
field names to different languages after some fields already mapped
- <Bugfix> - Corrected issue when mapping fields
using keyboard (introduced in version 1.0.6)
- <Change> - Updated error reporting system
Version 3.0.6 - Released: 2010.2.14
- <Change/Bugfix> - Removed StoreID from export
mapping field list - not for use in QuickPort/DataPort export functions
- <BugFix> - Corrected export issues related
to Account and EntryID causing an error under some conditions
- <BugFix> - Corrected error exporting to MS SQL table
under certain conditions
Version 3.0.5 - Released: 2010.2.10
- <Change> - Initialization
processes modified to minimize issues with hosted and disconnected
Exchange accounts
- <BugFix> - Some numeric field types
not imported into target text field
- <BugFix> - EmailDisplayAs not formatted
according to default setting in all cases
- <Bugfix> - Text (CSV etc) records with no data
in any fields generated an error (not the same as a blank line in the
text file which did not result in an error)
- <Change> - (Add User Fields) button remained
visible when template recalled using a custom form
- <Change> - Internal component updates
Version 3.0.3 - Released: 2010.1.28
(this update should be installed by anyone running a previous version of QuickPort)
- <Change/BugFix> - Format settings for
FullName, FileAs and EmailDisplayAs fields changed to one of the
standard options be default and corrects issue where FullName and/or
FileAs fields were not being correctly updated. These settings are
independent of Outlook settings and must be set accordingly for desired
option (see help file for more info)
- <BugFix> - Date/Time values were not always
corrected to/from UTC/Local values
- <Change> - Corrects intermittent problem
where Outlook issues an "Early Termination" message when
importing to a contact folder using a custom form. Outlook is not used
for any QwkPort functions but is required to retrieve custom form
information. This problem only occured if Outlook was running at the
same time as QuickPort and a custom form was in use.
- <Bugfix> - When recalling <last> import
import - Full Name fields not updated
- <BugFix> - Text file header not processed
correctly when <last import> run repeatedly
Version 3.0.2 - Launched: 2010.1.4