CMSMLS Server Counts Don't Match Actual Records Returned
We are seeing that the counts we are getting back are higher than the actual number of records we get back from our queries.
Example:
When we send this query with a request for a count only, we are getting back a count of a total of 25338 for all matching listings in the RE_1, LD_2, and MU_3 classes:
(L_UpdateDate=2014-01-01+)
But when we send the same query and request the L_ListingID value for all matching records, we are getting only 23462 records back.
We suspect that the difference between what the counts are and what we are actually getting back from our queries is caused by some query quota/limits on the MLS server, such as a restriction on how many IDs we can pull at once and another restriction on how many full records we can pull at one time.
For example, when we attempted to pull all L_ListingID values for all listings in the RE_1 class, we consistently only get exactly 20,000 L_ListingIDs back, but the count indicates that there are actually more than 21,000 records in that class.
Does Central MS MLS have limitations on their system, and if so, what are they? Thanks!
Comments
Please specify the account name you are using?
There are normally limits set for the number of records per transaction.
These limits can vary by account profile.
When searching and returning the L_ListingIDs are you passing Limit=NONE?
Hi! UN is RETS_465
When searching and returning the L_ListingIDs are you passing Limit=NONE?
No, we batch through and pass Limit=2500 for these queries.
If you are batching and updating the 1 based offset correctly it should return all records.
Got it thanks! Can you let us know if there are any query limits or quotas that might apply?