Records Available but no Data
We are receiving a ton of listings in the feed for the Santa Fe Association of Realtors that have no data. Can you please provide clarification as to why these listings are being presented in the data feed if they do not have data? Please see the partial list of ID's below along with the credentials in use.
http://sfar.rets.paragonrels.com/rets... UN: 6248
201002020 201002586 201004297 201004429 201005015 201005016 201006182 201006188 201102676 201104755 201200359 201200362 201200711 201202799 201203581 201203919 201204221 201204278 201204364 201205058 201300914 201303282 201303515 201303588 201303837
Comments
Not sure what you mean by "no data".
What specific field data is missing?
I was able to download all 25 MF_4 listings using that account and there is data present.
OK, looks like this is specific to RE_1. Here is an example of a listing that we cannot pull any data for: 201702806. Looks like there are roughly 57k listings to where there is only data for about 16K.
I still don't understand what you mean when you say data?
Are you meaning that the records aren't being returned?
I was just able to pull 201702806 without issue using the account.
Or do you mean specific field values are are empty?
I apologize, the issue has been clarified.
The issue is that we are not able to extract all 50k RE_1 records running a backfill because the backfill gets interrupted in the middle with this error code: 20036 message: miscellaneous server error and we cannot continue from where we stopped because the dataset is not ordered by the date we are assuming it would be(L_UpdateDate).
Questions: We noted querying the dataset that it is not ordered by L_UpdateDate, is the data set ordered by some date field that we can use as reference when paginating? What causes code: 20036 message: miscellaneous server error. ? are there any rate limits? The page size goes up to 2500 records max, what is the suggested page size that would work better for this feed?
The data is returned in key field order (not date), so for Property it would be L_ListingID.
Paragon RETS does support Offset/Limit functionality so you can use that if you need to..
As far as batch size, your account is limited to 2500, so you can use or less.
OK, that should take care of it. Thank you for the information and your patience!
Were you able to get this working?