Ask Your Question

A way to get around 20203 error in RETS Connector

asked 2016-10-26 12:53:42 -0600

We are getting RETS error:

RETS Status code = 20203: Undecoded values were sent: Miscellaneous Search Error. Lookup: value ProsperVal not found in Lookup table SchElem_Lkp_1 for Resource 1. [LM_char10_68]

Because of this error, we cannot pull all the data from RETS connector. I was told via an MLS support that Paragon says there are ways to around this in the RETS Connector. How can we set this up?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2016-10-26 13:45:07 -0600

updated 2016-11-03 13:49:28 -0600

The only way I know to get around it would be to exclude the column that contains the invalid lookup from the result set. Or to have your search criteria include only the valid values for that column, skipping the invalid records.

You could also pull the data as COMPACT instead of COMPACT-DECODED then you could handle invalid lookups client side however you want.

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2016-10-26 12:53:42 -0600

Seen: 228 times

Last updated: Nov 03 '16