RETS Support Article

The following steps illustrate how the sync algorithm works:

1. The RETS client sends a request to the RETS server using LastModifiedDateTime >= SomeDate SomeTime in the Query argument and selects four or less columns, such as MLNumber, LastModifiedDateTime, PictureModifiedDateTime, and PictureCount.

Here is an example of this type of search:

The RETS server will return an unlimited number of records to the RETS client that have changed since the LastModifiedDateTime.

2. The RETS client builds a DB table locally and compares this search result data to what it already has in its own database. The RETS Client can now determine when changes were made to any of the search result file from Step 1 and can subsequentially update its own records from the RETS server for those MLNumbers.

3. The RETS client sends a request to the RETS server using a string delimited list of MLNumber values in the Query argument and leaves the Select argument blank. The response will contain a complete data set for those records that were requested. The RETS client keeps sending these search requests to the RETS Server until it has all the records it needs.

Here is an example of this type of search:

4. The RETS client now has all the changed records and is fully synchronized with the RETS server.

If you would like a further explanation as to why Rapattoni suggests this method or how the sync algorithm works, please feel free to contact Rapattoni RETS Support. We will be happy to assist you.