What's Included and New - Version 1.0.0.0

Sieve Merge Purge

Scrubs - Data Cleansing

 

Analysis Report added to all merge purges.

A new Analysis report has been added to all merge purges. After a run it can be accessed by clicking on the Analysis button in the Ribbon menu.

Dupe Analysis Menu Button 

After a merge purge is completed a Duplication Listing report is automatically displayed in the Output Pane. The Dupes column shows the total number of records that have matched.

Duplication Counts

It acts more like a summary report and does not show how many records were removed by each file.

The Analysis Report will break these values down.

Duplication Analysis Report

Removing of unwanted duplicate records added to grid.

There are instances where a merge purge run has produced undesirable results based on your settings. If you feel that a match should not be considered as such, you can manually remove it.

At the end of a run an interactive data grid is displayed. Use this grid to verify the match results.

Remove unwanted duplicates

Based on the settings for the run that produced this, records with Parent Order 2395 and 2068 were considered duplicates. If you feel that the record being matched against, Parent Order 2068 should not be a duplicate record. You can double-click on the entry to mark it as a non match record.

This yellow band indicates that the record will not be included in any of the counts report or be marked when you update you input file.

To recall the entry double-click on it again and it will be considered a duplicate record.

Record level priorities not calculated correctly.

Quantities on the Duplication and Analysis reports were not being calculated correctly when codes and priorities were used at the record level.

This has been corrected.

Incorrect labels when multiple addresses used in a merge purge.

When adding multiple addresses to a merge purge task the labeling of the Address items was incorrectly performed.

This is now fixed.

Pre-defined exception for fields named ID.

When a table is added to a task Pre Post Office attempts to map commonly used field names to task items. User fields that were named “ID” cause an application exception.

This has been addressed.

Address Parser now identifies company names.

When a company name was contained in an address line being parsed, it was extracted to an address line.

Example

Original input data: Address1: IBM Corp Address2: 10044 108th Street Address3: Suite 596 Address4: Edmonton, AB T6S 1C6

This update version of the Address Parser now ignores the company name line and only extracts address related lines to output fields.

Extracted output data: Parsed Address1: 10044 108th Street Parsed Address2: Suite 596 City: Edmonton Province: AB Postal Code: T6S 1C6

IBM Corp is ignored since it's not an address line but a company name.