[Rets-dev] Newb client query question
Alex Makhanko
Alex.Makhanko at topproducer.com
Thu Oct 19 14:18:09 CDT 2006
Here is an example of a query that works.
===>>>Send:
GET
http://somemls.rets.interealty.com/Search.asmx/Search?SearchType=Propert
y&Class=1&Limit=300&QueryType=DMQL2&Format=COMPACT-DECODED&Query=(242=AC
T),(152=850000-855000),(33=3) HTTP/1.0
<<<===Receive:
HTTP/1.1 200 OK
Connection: close
Date: Thu, 19 Oct 2006 19:14:57 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
RETS-Version: RETS/1.7
RETS-Server: Interealty-RETS/1.5.47.0
Set-Cookie: RETS-Session-ID=bdkt0u55lyxhcvmtnaabh045; path=/
Cache-Control: private, max-age=0
Content-Type: text/xml
<?xml version="1.0"?><RETS ReplyCode="0" ReplyText="Operation
Successful"><DELIMITER value="09"/><COLUMNS> sysid 1628 50
1699 69 70 1719 1755 81 82 83 84
85 86 87 88 33 276 79 1674 64
1630 74 1801 90 34 93 1594 1777 1779
1778 1780 1781 1767 1759 1768 1760 1769 1761
1770 1762 1771 1763 1772 1764 1773 1765 1774
1766 1775 1776 91 89 100 277 1713 1680
278 20 103 104 292 105 293 101 102
106 107 1596 109 111 279 113 280 124
125 281 128 129 130 1600 282 1715 1693
134 294 135 1602 283 137 138 139 10
284 1697 141 142 143 66 1756 233 164
1668 1670 1604 1799 1676 1608 1672 18 36
1612 1614 1616 149 1606 1812 1678 1620 150
1622 1618 152 1610 156 1682 157 159 285
161 63 1701 287 1810 127 296 171 172
286 173 179 180 174 175 295 176 177
178 181 1695 12 1624 1664 16 288 193
71 72 97 195 196 245 200 201 1707
203 204 290 13 206 289 5 1626 1723
1709 3 208 1793 291 297 298 1805 300
155 1632 2 1634 19 301 92 232 17
1703 1705 240 302 1803 242 60 246 244
191 1816 1684 303 1642 249 1640 1791 1646
304 1758 305 235 1648 1638 1650 1688 256
257 306 259 1576 307 262 263 1654 308
62 268 1711 1686 299 56 1660 47 48
1662 </COLUMNS><DATA> 16117622 2150 S
OCEAN # 4-C 0 100 4140 4140 15 13
14 13 0 0 0 0 3 N
Y EASY TO SHOW. VACANT MUST COORDINATE W/LA BILL 305-926-8539
ORHIS ASSITANT SUSAN 305-926-8588. THEY WILL OPEN IT UP FOR YOU 4
0 0 DELRAY BEACH 0 0
0 0 0 0 0
0 0 0 0 2.5
2.5 2.5 CBS CENTRAL,ELECTRIC PALM
BEACH 0 0 LT 4 FLOORS FORMAL,EAT IN KITCH
0 0 12 12 LINTLINTON TO A1A, GO SOUTH 1/4 MILE TO
GREY AND WHITE BLDGS ON RIGHT 2005-10-07T00:00:00
WASHER,DRYER,REFRIGERATOR,RANGE,DISHWASHER,ELEC WTR HTR,DISPOSAL
0 0 CARPET,CERAMIC TILE,LINOLEUM 0 0 E
3 UNFURNISHED 2.0 PB05 CONDO 0 1
CENTRAL,ELECTRIC M 1000 MON 1 WLK IN
CLOS,ELEVATOR 14 10 0 2006-05-11T07:02:41
20001472
-----Original Message-----
From: rets-dev-bounces at rets.org [mailto:rets-dev-bounces at rets.org] On
Behalf Of Brad Peterson
Sent: Thursday, October 19, 2006 12:09 PM
To: rets-dev at rets.org
Subject: [Rets-dev] Newb client query question
Our product's application has successfully integrated with a Tempo RETS
1.5 system, and that was a breeze.
But now I'm trying to integrate with an Interealty RETS 1.5 system, and
I'm pulling my hair out in frustration. I've spent 3 days researching
and pouring over the documentation, but I cannot seem to do a meaningful
query. I would be very grateful for some guidance in the right
direction.
Currently, it seems that this RETS server is very picky about how it
processes a query. I also cannot get it to perform a query on what I
ask it to. For example, the following requests did not work for me:
Search.asmx/Search?SearchType=Property&Class=1&Query=*&Limit=25 (Result
was <RETS ReplyCode="20203" ReplyText="Query type is not DMQL or
DMQL2.">)
Search.asmx/Search?SearchType=Property&Class=1&Query=(2=1*)&Limit=25&Que
ryType=DMQL2
(Result was <RETS ReplyCode="20203" ReplyText="Missing close parenthesis
on subquery.">)
What finally retrieved results was this:
Search.asmx/Search?SearchType=Property&Class=1&Query=2=1*&Limit=25&Query
Type=DMQL2
Unfortunately, it seems that no matter what I put in for the Query, such
as Query=2=* or Query=123123123=* or Query=*, I get the same results
over and over.
So my question is...what am I doing wrong? If I can just see how to
query off one field, I can probably go from there and complete
everything else I need. But I can't ever seem to get queries to give me
anything than the same set of results over and over again.
To help, here is some info returned from a
GetMetadata.asmx/GetMetadata?type=METADATA-SYSTEM&id=* request
<Resource>
<ResourceID>Property</ResourceID>
<StandardName>Property</StandardName>
<VisibleName>Property</VisibleName>
<Description>MLS Property Table</Description> ...
<METADATA-CLASS System="LASRETS" Resource="Property"
Version="13.37.90495" Date="Tue, 26 Sep 2006 19:01:35 GMT">
<Class>
<ClassName>1</ClassName>
<StandardName>ResidentialProperty</StandardName>
<VisibleName>RES</VisibleName>
<Description>Residential</Description>
<METADATA-TABLE System="LASRETS" Resource="Property" Class="1"
Version="13.37.90495" Date="Tue, 26 Sep 2006 19:01:35 GMT">
....
<Field>
<SystemName>2</SystemName>
<StandardName/>
<LongName>Approximate Acreage</LongName>
<DBName/>
<ShortName>Acreage</ShortName>
<MaximumLength>8</MaximumLength>
<DataType>Decimal</DataType>
<Precision>3</Precision>
<Searchable>1</Searchable>
<Interpretation>Number</Interpretation>
<Alignment/>
<UseSeparator>0</UseSeparator>
<EditMaskID/>
<LookupName/>
<MaxSelect>0</MaxSelect>
<Units/>
<Index>0</Index>
<Minimum/>
<Maximum/>
<Default>0</Default>
<Required>0</Required>
<SearchHelpID/>
<Unique>0</Unique>
</Field>
...
Brad Peterson
_______________________________________________
Rets-dev mailing list
Rets-dev at rets.org
http://lists.rets.org/mailman/listinfo/rets-dev
More information about the Rets-dev
mailing list