Importer jobs

Also, I just looked, everything seems to have been pulled in as a draft.

You guys initially setup my importer jobs.
2 of them for residential.
I’d like to break them into smaller jobs.
Best I can tell is the delineating point is this in the Property Query:
(Apx_Yr_Blt=1000-1980) in the first importer job,
(Apx_Yr_Blt=1981-2015) in the second importer job.
A few questions arise:
I suppose the way to deal with this is break those ranges up?
Shouldn’t the last job go to the current year?
I guess I have to update that last query each year?
Isn’t there a better way to do this?

Hello.

Here is some instruction about DMQL Query – https://www.flexmls.com/developers/rets/tutorials/dmql-tutorial/

You could use something like
(number_field=2+)

Also here is some common reasons for such issue – https://wp-property.github.io/addons/importer/properties-not-published-or-pending-images-download-for-wp-property-importer.html

Regards.

Am I correct in beleiving that (Apx_Yr_Blt=2005-2018+) will make sure the newest construction will show?

no, you will need such Query (Apx_Yr_Blt=2005+)

Ok, I want to use something other than year.
How about sq ft?
How can I search for the breakdown of square footage to ensure I get a few smaller similar sized groupings?

Only by testing different values. While running the import you will see how many properties refers to this group.

We break out our jobs by Counties (“L_Area” field in our feed).
Our Property Query (DMQL) is:
(L_StatusCatID=1),(L_Area=23,28,38)

Your feed provider should have a document that can tell you what field County is in, and what IDs go with what County. Or use https://retsmd.com/

In our feed images take a long time to import as well. Maybe 4 hours, for 400 properties. Never timed it.

Yes, properties seem to be import in Draft state, then get changed to published.

Do I need to do something to tell these groups not to delete the other like groups listings?
I made an adjustment to a group cut the size of the download in half.
It delete a bunch of properties.
Does it delete properties that don’t fit the RETS query?

>Does it delete properties that don’t fit the RETS query?

there is an option to delete properties which are no longer in the feed( that also mean no longer in Property Query which you have set up),
so using that option properties will be deleted.

got it.

To be clear, I have two imports of the same property type AND “Remove properties that are no longer in source XML…” is checked in BOTH imports, this is correct?

Yes. I have the same set up: multiple feeds with “Remove properties that are no longer in source XML…” checked on all of them. A property that is imported via feed “A”, will not be touched/deleted by feed “B”.

• This reply was modified 6 years ago by Kimball31.

Thanks, I have now confirmed that, too.

The image download job is a bit confusing, mostly because there is no indication, that I’m aware of, if it is still running or if you have an issue.