Hello,

I have a listing type (residential rentals) that has an immense number of listings. I have never had success importing them all at once, so I've had to break down the import into smaller chunks based on price ranges. My RETS provider does not support offset, so I have been using this query:

Offset Not Supported (Query based on price field)
(246=A),(137=1000-1500)

246 is "status" and 137 is list price.

I then run an import, allow it to complete, and then change the price range (137=1500-2500) and import again. Repeat...

I have discovered that any previously-imported listings from the prior price range(s) now have a status of "0" (Inactive). Why would running a new import change their status? I have never checked the "mark all listings for update" option. Is there a way to avoid this issue, or a better way for me to write my query that might allow them all to import with a single query?

Thanks!

Comments

hockey2112 created an issue. See original summary.

shauntyndall’s picture

shauntyndall commented
Status: Active » Postponed (maintainer needs more info)

@hockey2112 I believe others have dealt this this by setting up multiple connections and having a subset query (like you are using) under each connection. That will allow dRealty to loop over the connections and maintain synchronization with each subset of the Residential Rentals.

hockey2112’s picture

hockey2112 commented

That is a very interesting and smart solution/workaround. I'll give it a shot. Thanks!

Meanwhile, is there a particular reason why the status of imported listings changes when you change the query for that listing type? I suppose it might mean that you no longer want listings that match the previous query, and therefore they should be marked as inactive so they can be removed...