Not logged in - Login / Register


R
e
q
u
e
s
t

a

d
e
m
o
< back

Data Masking Components: City Names Dynamic

"CityCity Names Dynamic"Dynamic


API Reference, CLR Reference (links)

Usage Instructions:

Purpose

The purpose of the component is to mask such values as Account or Patient Numbers that often consist of the combination of Alpha and Numeric characters and are not formed by a specific rule.

Algorithm

VariationPRESERVING ofREFERENTIAL RandomINTEGRITY Character Permutation AlgorithmSUBSTITUTION

Description

The Masking City Names Dynamic component changes The City name into another city name chosen from a list that includes the names of America’s 1000 largest cities. The component guarantees consistent transformation of values but does not guarantee uniqueness.

Usage Instructions:

1. Configure a source that contains the column with alphabetical and numeric characters. The data in the column may also include any other character that will be treated as a separator.
2. Drag and Drop City Names Dynamic masking component, connect the source and the City Names Dynamic component with the source's precedence constraint:
GA 3. Now, the precedence constraint (the blue arrow) passes proper meta-data to the City Names Dynamic component. If you click on constraint, you will see:
4. Now that the metadata for the City Names Dynamic masking component exists, and values are passed into the data masking component, please open the component editor:
5. In the second tab, there are input columns. Please check-mark only one column, the one that you will be masking with City Names Dynamic algorithm:
6. This will create an extra column with the prefix “Masked_”.
7. Create a connection manager for the destination and configure source component for the destination. In the connection manager, in the tab “Mappings”, specify that you want newly created Field_Masked to be a field replacing the original value. For that, just click on the available input columns, choose the masked value, and map to the “Available Destination Columns”
8. Now, all the configurations are complete for the valid values. You can run the package with the City Names Dynamic Data Masking component, and see the results of data masking:

Error Handling

9. If, however, there are invalid values in the package's source, one would need to configure error handling. Invalid values are those that are not conforming to the rules of the entity. To handle invalid values, each data masking component has error handling precedence constraint. One needs to create error destination connection and connect red arrow (error handling constraint) with this destination. As the connection is made, one needs to configure the state of failure: “Fail”,”Ignore” or “Redirect”.
10. It is recommended that one re-directs the output into the error destination, so that later one be able to analyze and process data for quality purposes. The City Names Dynamic components errors are the only ones not recommended for further processing as it is truly hard to break their format.
11. It is our suggestion that with City Names Dynamic component one should not process erroneous data without further analysis at all.

Download Example ###**

Download a Trial