First time here? Check out the FAQ!
Ask Your Question
0

bad lookup for precn in ConstrStat_Lkp_7

This causes processing to crash. This one is rental table There is no option for PRECN in any class for ConstrStat_Lkp_7

ValueError: unknown XML element <element 'rets-status'="" at="" 0x3eaf480=""> with attributes {'ReplyText': 'Undecoded values were sent: Miscellaneous Search Error. Lookup: value PRECN not found in Lookup table ConstrStat_Lkp_7 for Resource 1. [LM_char50_8] ', 'ReplyCode': '20203'}

bscdata's avatar
bscdata
asked 2016-10-06 11:30:53 -0500, updated 2016-10-06 11:37:22 -0500
edit flag offensive 0 remove flag close merge delete

Comments

What's even worse is that error is coming up when I'm only asking for ListingID to be sent:

<data> 4176986 </data> <data> 4176995 </data> <data> 4176996 </data> <maxrows/> </rets>

  • Re-using existing connection! (#0) with host (nil)
  • Connected to (nil) (208.93.242.142) port 443 (#0)
imaxdev's avatar imaxdev (2016-10-06 22:42:30 -0500) edit
more
  • delete

GET /rets/fnisrets.aspx/NEREN/search?SearchType=Property&Class=RE_1&Query=%28L_UpdateDate%3D2016-09-18T22%3A45%3A00%2B%29&QueryType=DMQL2&Count=1&Format=COMPACT-DECODED&Limit=1000&Offset=5001&Select=L_ListingID&StandardNames=0 HTTP/1.1

imaxdev's avatar imaxdev (2016-10-06 22:43:48 -0500) edit
more
  • delete

Authorization: Basic CITY RTE 302 TO E.BARRE, L ONTO COBBLE HILL RD, THEN 4TH R ONTO SUNNYSIDE, GO TO THE END ON RIGHT. Susan Arguin 13809

imaxdev's avatar imaxdev (2016-10-06 22:43:58 -0500) edit
more
  • delete

<rets-status replycode="20203" replytext="Undecoded values were sent: Miscellaneous Search Error. Lookup: value PRECN not found in Lookup table ConstrStat_Lkp_1 for Resource 1. [LM_char50_8] "/> <maxrows/> </rets>

imaxdev's avatar imaxdev (2016-10-06 22:44:07 -0500) edit
more
  • delete
add a comment see more comments

2 Answers

1

UPDATE: 2016-10-11 17:30 CST - The metadata refresh has been completed which should fix the undecoded values.

bwolven's avatar
bwolven
answered 2016-10-11 17:23:29 -0500
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments
1

i have created a workaround. the issue was there were 2 error elements that are returned. "rets-status" is for failures in lookup and "rets" is returned if there is no data.

i changed script to accept either and it is fine. it used to be "rets-status" for any failure.

bscdata's avatar
bscdata
answered 2016-10-07 15:08:59 -0500
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments

Your Answer

Login/Signup to Answer