First time here? Check out the FAQ!

Undecoded Metadata values

We seem to have a consistent issue with undecoded metadata values coming down that cause our data downloads to fail. How do I report this and what can I do to avoid the issue?

SmarterAget's avatar
asked 2015-06-18 09:38:07 -0500
bwolven's avatar
updated 2015-12-08 16:39:14 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


Please take a look at What does Unencoded Error indicate in a RETS Response?

Some of the possible reasons: * A lookup value was removed but it is still referenced in one of the records. * The static metadata is out of sync with Paragon lookup values and needs to be refreshed. The refresh would synchronize the lookups in Paragon with the static metadata used by RETS.

vendorsupport's avatar
answered 2015-06-18 09:53:23 -0500
edit flag offensive 0 remove flag delete link


would that metadata refresh need to be done by my rets client or the MLS?

SmarterAget's avatar SmarterAget (2015-07-07 10:24:23 -0500) edit

Your MLS would need to update the system metadata, and then you would need to refresh locally in the client.

vendorsupport's avatar vendorsupport (2015-07-07 11:57:59 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer