Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Multiple-Instance Ports

Multiple-Instance Ports

Many types of address data can occur more than once in an address. You can select multiple instances of a port when the address contains multiple cases of a data element.
A multiple-instance port can contain up to six instances. Many addresses use one instance of a port for each data element that they contain. Some addresses use a second instance of a port. A small set of addresses use more than one port instance.
Often, the first instance of a port is the primary name or the largest area that the port identifies. You must verify the relationship between the port instances for any port that you select.

Street Complete Ports Example

A United Kingdom address record can contain two street names when one street is part of a larger street plan.
The following table contains an address that uses two Street Complete ports:
Port
Data
Street Number Complete 1
1A
Street Complete 1
THE PHYGTLE
Street Complete 2
SOUTH STREET
Locality Name 1
NORFOLK
Postcode 1
NR25 7QE
In the example, the street data in Street Complete 1 is dependent on the street data in Street Complete 2. The data in Street Number Complete 1 refers to the data in Street Complete 1.
Although Street Complete 1 specifies the location of the mailbox, Street Complete 2 might be the larger street.

Contact Ports Example

An address record can contain multiple contacts when each contact is a member of the same household.
The following table contains an address that uses two Contact Name ports:
Port
Data
Contact Name 1
MR. JOHN DOE
Contact Name 2
MS. JANE DOE
Formatted Address Line 1
2 MCGRATH PLACE EAST
Formatted Address Line 2
ST. JOHN'S NL A1B 3V4
Formatted Address Line 3
CANADA
In the example, the organization can decide on the precedence to apply to Contact Name 1 or Contact Name 2. The Address Validator transformation does not prioritize the contact data.
If you format addresses for printed output, you might use multiple instances of the Formatted Address Line ports. You can select up to 12 Formatted Address Line ports.

0 COMMENTS

We’d like to hear from you!