[libRETS-users] Latest librets .NET version

[Keith T. Garner]

Robert Burdick wrote:
> I get a number of invalid select errors using librets for .NET against a
> RETS 1.5 compliant server.  The same queries done directly through a web
> browser work just fine.

I say this so much that I think it'll be put on my headstone:  a web browser
is not a RETS client.

While sometimes something working in a browser tells us something, more of
than not, it confuses issues.  For example, most RETS 1.5 servers also
support RETS 1.0.  One of the telling differences between 1.5 and 1.0 is the
RETS-Version header.  It didn't exist in RETS 1.0, its required in RETS 1.5.
 Many servers (variman being a prime example) drop down to acting like a
RETS 1.0 server when it does not see that header.  Your browser does not
send this header, so there could be differences in how a server responds.

In any case....

> The exception that gets thrown by librets is an
> ArgumentOutOfRange exception, if I add the State meta data item to my
> SetSelect statement.

The message in that exception is the "invalid select" you mention below?
Hmm...  Looks like our exceptions are being mapped to a weird native .NET
exception.  We'll have to look into that.  However, that isn't your problem
right now...

> Could there be a problem with the code that parses the string passed to
> SetSelect before the actual RETS query is sent?

libRETS does no pre-parsing or translation of that information.  In fact, it
is sent along almost exactly as you see it.  The only thing that *should*
happen as far as I can tell, would be to URL escape it.

> mSearchRequest.SetSelect("ListingID,PublicRemarks,StreetNumber,StreetName,Ci
> ty,State,PostalCode,Property.Age,Cooling,FirePlace.Details,Heating,Stories,L
> otSizeArea,LotSizeArea.Units,LotSizeLength,LotSizeWidth,ListingArea,ListPric
> e,ListingStatus,BathroomFeatures,Baths,BathRange,BedroomDescription,Beds,Oth
> erAreas,Pool,PropertyStyle,Property_HotTub,Roof,View"); //Gives an invalid
> select: State error

That message of "invalid select: State" is definitely one coming from the
server and not generated within libRETS.  Since you've narrowed it down to
one field, I'm thinking its a server issue and not a client one.  Especially
since that error you receive is coming from the server.

Keith

-- 
  Keith T. Garner - Managing Director - Center for REALTOR® Technology
   kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt