Personator Identity:Result Codes: Difference between revisions
Created page with "{{PersonatorWorldNav |ResultCodeCollapse= }} {{CustomTOC}} ==Result Code Use== Melissa Data's products use a result code system to indicate data quality; the status and any..." |
No edit summary |
||
| Line 7: | Line 7: | ||
==Result Code Use== | ==Result Code Use== | ||
Melissa | 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=== | ===Example=== | ||
Revision as of 19:41, 20 March 2017
| Personator Identity 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 Result Codes for a list of Melissa Data's 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.