Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Address Verification (On-Premises) 5.16.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Getting Started with Informatica Address Verification (On-Premises)
  3. General Settings
  4. Input Parameters
  5. Process Parameters
  6. Address Enrichments
  7. Result Parameters
  8. Output Fields
  9. Assessment Codes and Return Codes
  10. Frequently Asked Questions
  11. Appendix A: Geocode Countries
  12. Appendix B: CASS Return Codes

Developer Guide (On-Premises)

Developer Guide (On-Premises)

Back Next

PreferredScript Examples

PreferredScript Examples

The following examples show how the
PreferredScript
 attribute functions in different scenarios.

Japan address input in Kanji script

The following Japan address is in Kanji script. The
PreferredScript
 attribute is set to PRESERVE_INPUT. 
<InputData>
	<AddressElements>
		<Country Item="1" Type="NAME">JAPAN</Country>
		<Locality Item="1" Type="COMPLETE">大阪市</Locality>
		<Locality Item="2" Type="COMPLETE">都島区</Locality>
		<Locality Item="3" Type="COMPLETE">内代町</Locality>
		<PostalCode Item="1" Type="UNFORMATTED">〒534-0013</PostalCode>
		<Province Item="1" Type="COUNTRY_STANDARD">大阪府</Province>
		<Street Item="1" Type="COMPLETE">２丁目</Street>
	</AddressElements>
</InputData>
The output is in Kanji script: 
<FormattedAddressLine Line="1">JAPAN〒534-0013大阪府大阪市都島区内代町２丁目</FormattedAddressLine>

Japan address input in mixed script

The following input address contains both Latin and Kanji scripts. 
<InputData>
	<AddressElements>
				<Country Item="1" Type="NAME">JAPAN</Country>
				<Locality Item="1" Type="COMPLETE">ŌSAKA-SHI</Locality>
				<Locality Item="2" Type="COMPLETE">MIYAKOJIMA-KU</Locality>
				<Locality Item="3" Type="COMPLETE">UCHINDAI-CHŌ</Locality>
				<PostalCode Item="1" Type="UNFORMATTED">534-0013</PostalCode>
				<Province Item="1" Type="COUNTRY_STANDARD">ŌSAKA-FU</Province>
				<Street Item="1" Type="COMPLETE">2 CHŌME</Street>
				<Organization Item="1" Type="COMPLETE">オ</Organization>
	</AddressElements>
</InputData>
The output in this case, where the input contains both Latin and Kanji scripts, is in Kanji script , which is the default script of the Japanese address database. 

<FormattedAddressLine Line="1">〒534-0013大阪府大阪市都島区内代町２丁目オ</FormattedAddressLine>

Russia address input in Latin script

The following input address contains Latin script. 
<InputData>
 <AddressElements>
   <Country Item="1" Type="NAME">RUSSIAN FEDERATION</Country>
   <Locality Item="1" Type="COMPLETE">Majma</Locality>
   <PostalCode Item="1" Type="UNFORMATTED">649100</PostalCode>
   <Province Item="1" Type="COUNTRY_STANDARD">Altaj</Province>
   <Street Item="1" Type="COMPLETE">ul. Celinnaâ</Street>
   <Number Item="1" Type="COMPLETE">1</Number>
 </AddressElements>
</InputData>
The output in this case is in Latin script because of the PRESERVE_INPUT setting. 
<FormattedAddressLine Line="1">ul. Celinnaâ 1</FormattedAddressLine>
<FormattedAddressLine Line="2">Majma</FormattedAddressLine>
<FormattedAddressLine Line="3">Altaj</FormattedAddressLine>
<FormattedAddressLine Line="4">649100</FormattedAddressLine>

Russia address in mixed input that contains Cyrillic and Latin scripts:

The following input address contains both Cyrillic and Latin scripts. 
<InputData>
 <AddressElements>
   <Country Item="1" Type="NAME">RUSSIAN FEDERATION</Country>
   <Locality Item="1" Type="COMPLETE">Majma</Locality>
   <PostalCode Item="1" Type="UNFORMATTED">649100</PostalCode>
   <Province Item="1" Type="COUNTRY_STANDARD">Altaj</Province>
   <Street Item="1" Type="COMPLETE">ul. Celinnaâ</Street>
   <Number Item="1" Type="COMPLETE">1</Number>
   <Organization Item="1" Type="COMPLETE">й</Organization>
	</AddressElements>
</InputData>
If you set
PreferredScript
 to PRESERVE_INPUT, the output contains only Cyrillic because that is the default script of the Russia reference address database. 
<FormattedAddressLine Line="1">Й</FormattedAddressLine>
<FormattedAddressLine Line="2">ул. Целинная 1</FormattedAddressLine>
<FormattedAddressLine Line="3">Майма</FormattedAddressLine>
<FormattedAddressLine Line="4">Алтай</FormattedAddressLine>
<FormattedAddressLine Line="5">649100</FormattedAddressLine>
0 COMMENTS
We’d like to hear from you!