Personator Consumer:Result Codes: Difference between revisions
m Admin moved page Personator:Result Codes to Personator Consumer:Result Codes |
No edit summary |
||
| Line 28: | Line 28: | ||
|} | |} | ||
Be sure to reference [[Result Code Details#Personator|Personator Result Codes]] for a list of Personator result codes. | Be sure to reference [[Result Code Details#Personator Consumer|Personator Consumer Result Codes]] for a list of Personator Consumer result codes. | ||
===Understanding the Code=== | ===Understanding the Code=== | ||
Latest revision as of 23:07, 25 July 2019
| Personator Consumer Navigation | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| Sample Code |
Result Code Use
Melissa's products use a result code system to indicate data quality; the status and any errors. These result codes are four-character codes (two letters followed by two numbers), delimited by commas. Result code definitions are shared among Melissa products.
Example
An example returned result code string:
VR01
Instead of looking at multiple properties and methods to determine status, you can look at the output of the results parameter.
From this output you can determine that the address is:
| Code | Short Description | Long Description |
|---|---|---|
| VR01 | Individual and Phone Match | The individual name and phone match. |
Be sure to reference Personator Consumer Result Codes for a list of Personator Consumer result codes.
Understanding the Code
To fully understand result codes, you need to know them. Knowing what codes are possible and what they indicate will be key in building an effective application. It is useful to know all the codes, but this does not necessarily mean you will use them all. Just because you have a toolbox, doesn't mean you will also try to use a screwdriver along with a hammer on a nail.