First time here? Check out the FAQ!
0

Elko County Association of REALTORS® - Queries are only able to pull 1 listing at a time

  • retag add tags

Queries are only working for 1 listing at a time, so if we try to load data with our usual RETS limit of 100 properties per query, it fails. Setting up our script to pull only one property at a time will result in extremely poor performance. Can we look into getting that rets limit raised?

Example: retsX -u 'EC_Wolfnet' -p 'XXXXXX' -l 'http://mlsservice.com:6103/rets/login' -v 'RETS/1.5' -a 'Wolfnet/1.5' -t Search -q 'Limit=NONE&QueryType=DMQL2&StandardNames=0&Count=1&Format=COMPACT-DECODED&SearchType=Property&Class=ResidentialProperty&Query=(ListingID%3D340006)'

works just fine, however when the query is for two listings:

retsX -u 'EC_Wolfnet' -p 'XXXXXX' -l 'http://mlsservice.com:6103/rets/login' -v 'RETS/1.5' -a 'Wolfnet/1.5' -t Search -q 'Limit=NONE&QueryType=DMQL2&StandardNames=0&Count=1&Format=COMPACT-DECODED&SearchType=Property&Class=ResidentialProperty&Query=(ListingID%3D340006,340021)'

it fails with the following error: <rets replycode="20206" replytext="Invalid Query Syntax: line 1:12: unexpected token: 340006"/>

MLSNotify's avatar
MLSNotify
asked 2018-10-15 09:51:08 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

What RETS URL are you using?
What I see above isn't Paragon RETS?

bwolven's avatar
bwolven
answered 2018-10-15 10:18:10 -0500
edit flag offensive 0 remove flag delete link

Comments

I apologize, the MLS is changing data vendors and this is NOT Paragon. Ticket can be closed out. Thanks.

MLSNotify's avatar MLSNotify (2018-10-15 10:56:16 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer