Options - dataflow_designer - spectrum_quality_1 - 23.1

Spectrum Data Quality Guide

Product type
Software
Portfolio
Verify
Product family
Spectrum
Product
Spectrum > Quality > Spectrum Quality
Version
23.1
Language
English
Product name
Spectrum Data Quality
Title
Spectrum Data Quality Guide
Topic type
How Do I
Overview
Tips
Reference
First publish date
2007
ft:lastEdition
2024-03-04
ft:lastPublication
2024-03-04T22:52:13.486265

The Write Exceptions stage enables you to select which field data is returned to the exceptions repository

Fields that appear in the table depend upon the stages that occur upstream in the dataflow. If, for instance, you have a Validate Address stage in the dataflow, you would see such fields as AddressLine1, AddressLine2, City, PostalCode, and so on in the Write Exceptions stage.

The order of the fields is determined by how they are ordered when they come into the Write Exceptions stage. You can reorder the fields by selecting a row and using the up Image of up button and down Image of down button buttons next to the table to move the row up or down in the table. The order you select here will persist for all users in the Data Stewardship Portal, but each user can reorder the fields within the Portal to their own liking.

Note: There is 1000 field limit when writing exceptions to Data Stewardship Portal. This count is cumulative across dataflows and stages. To avoid hitting this limit we recommend that you only include fields required to resolve exceptions. You can clear the Allow Viewing check box to pass through fields. They then do not contribute to the field limit. Only fields accessible in Portal contribute to the limit.

Table columns

Field Name

Select this check box to return field data to the exceptions repository. By default, this check box is selected for all fields. Clear the check box for any field that you do not want returned to the exceptions repository.

Allow Viewing

You may have input fields that you want in the repository but do not want to be viewable within the Data Stewardship Portal. This could be due to the field containing sensitive data or simply because you want to streamline what appears in the Portal. Check the Allow viewing box to designate which of the selected fields should be viewable once they are passed to the exceptions repository. By default, all fields are viewable. Uncheck the box for any field you do not want visible in the Portal.

Allow Editing

Select this check box to make fields editable in the Portal after they are passed to the exceptions repository. By default, the Allow editing column is checked for all fields in the table. Uncheck the box for any field you wish to be returned to the exceptions repository in a read-only state.

Lookup Name
Use the lookup function to assign a lookup to a field containing problematic data. You can select from the list of lookups that have been defined in the Data Stewardship Settings tool or you can manually enter the name of the lookup. Lookups can only be assigned to fields whose type is string. For more information, see Lookups.
Note: Lookups can be assigned only to fields whose type is string.

Option

Allow user to create Best of Breed records in Portal
Select this check box to perform manual record consolidation when data matches cannot be made using standard rules. This feature copies a selected record within a group and uses it instead of the duplicates for processing. This option is available only for grouped exception records that are generated from a matching job, which is identified by the presence of the CandidateGroup field or the CollectionNumber field. When you use this option, a read-only field called “CollectionRecordType” will be added to the exception record. You can see this field at the bottom of the list. Note that all options for that field are disabled.
Note: If your dataflow is also being configured for revalidation, you will need to manually add and expose the CollectionRecordType field in the Exception Monitor stage/subflow and the service itself.

After a Best of Breed record is added in the Resolve Duplicates view of the Data Stewardship Portal Editor, this field will be set to "BestOfBreed." If you choose to create best of breed records, you will be unable to use the Approve All option for those records in the Data Stewardship Portal. For more information about best of breed records in the Data Stewardship Portal, see Creating a Best of Breed Record.