[libRETS-users] Strange Error

[Bill Linker]

Is their server RETS 1.5 or 1.0? librets defaults to 1.5. I believe
authentication is handled a bit differently between the two versions.
Perhaps this "RETS Connector" app is defaulting to 1.0 and their server
is 1.0. The RETS version is probably a more likely cause than these, but
knock yourself out trying these things:

1) Check the metadata and make sure there is not another status field
that you should be using instead.
2) Check the metadata for fields 290 and 40 and make sure IsSearchable
is true
3) Try changing the format to COMPACT-DECODED
4) Try changing the QueryType to DMQL
5) Try some other query (try a simple one like listingID=######)
6) Try using an empty select list

When you have eliminated all possible alternatives within librets's
available options, you can then be a little more suspicious that the
error is on their end.

Bill Linker






-----Original Message-----
From: librets-users-bounces at crt.realtors.org
[mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Keith T.
Garner
Sent: Wednesday, December 19, 2007 10:48 AM
To: For discussion and help for and by the users of the libRETS C++
library
Subject: Re: [libRETS-users] Strange Error

It could be them not handling the encoded equals then.  That is the
proper
thing to do, but I'll have to noodle on this.

Keith

On 12/19/07 12:41 PM, Russ Perna wrote:
> Keith,
> 
> I had actually tried both way, and neither seems to work.
> 
> Thanks,
> Russ 
> 
> 
> Russ Perna
> --
> Senior Developer
> Prudential Rand Realty
> http://www.prudentialrand.com
> 845.825.8036
>  
>  
> 
> -----Original Message-----
> From: librets-users-bounces at crt.realtors.org
> [mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Keith T.
Garner
> Sent: Wednesday, December 19, 2007 1:16 PM
> To: For discussion and help for and by the users of the libRETS C++
library
> Subject: Re: [libRETS-users] Strange Error
> 
> 
> On 12/19/07 12:06 PM, Russ Perna wrote:
>> Maybe it could be something else then.
>>
>> This is the request from RETS Connector:
>> URI:
>>
/Search.asmx/Search?SearchType=Property&Class=1&Select=217&Format=COMP
>> ACT&Qu
>> eryType=DMQL2&Query=(290=%7CACT),(40=%7C440)
>>
>> This is the request from libRets:
>> URI:
>>
/Search.asmx/Search?Class=1&Count=1&Format=COMPACT&Query=(290%3dACT),(
>> 40%3d4 
>> 40)&QueryType=DMQL2&SearchType=Property&Select=217&StandardNames=0
>>
>> Does this tell you anything that I might be missing?
> 
> Yes, you are not querying the LOOKUPs with the syntax for querying
LOOKUPs.
> 
> Your query is "(290=ACT),(40=440)" when it should be
"(290=|ACT),(40=|440)"
>  In your example from RETSConnector, you can see a %7C in their
URLEncoded
> version.  %7C is | when decoded.
> 
> kgarner at copper [501]:irb
> irb(main):001:0> require 'uri'
> 
> irb(main):003:0> URI.unescape('(290=%7CACT),(40=%7C440)')
> => "(290=|ACT),(40=|440)"
> 
> 
> The RETS metadata is your friend.  Both of those tables should tell
you that
> their interpretation is LOOKUP.
> 
> Keith
> 
> --
>   Keith T. Garner - Managing Director - Center for REALTORR Technology
>    kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt
> _______________________________________________
> libRETS-users mailing list
> libRETS-users at crt.realtors.org
> http://mail.crt.realtors.org/mailman/listinfo/librets-users
> 
> 
> _______________________________________________
> libRETS-users mailing list
> libRETS-users at crt.realtors.org
> http://mail.crt.realtors.org/mailman/listinfo/librets-users


-- 
  Keith T. Garner - Managing Director - Center for REALTOR(r) Technology
   kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt
_______________________________________________
libRETS-users mailing list
libRETS-users at crt.realtors.org
http://mail.crt.realtors.org/mailman/listinfo/librets-users