Step 3. Compare Master List to Client Data Store

Any properties, offices, or agents in a client’s local data store that are not present in the master list must be removed.

For example, the master list will include a property only while it is active on the market and approved for distribution. Once the property is no longer active (e.g., sold, cancelled, or otherwise removed), it will be excluded from the master list and should be deleted from the client’s data store.

The master list also serves as a tool for data integrity. Steps 1 and 2 of the synchronization process should typically be enough for clients to maintain accurate datasets for all resources. However, if discrepancies arise between the LastUpdated values in the master list and the client’s local store (such as a missing or outdated property), these issues can be corrected in Step 4.

SHARE POST:

Facebook
Reddit
LinkedIn

AgentDetails Payload

Parent Cardinality Name Type Description Lookup AgentDetails 1 Name String The name of the Agent AgentDetails 1 ID Integer (Attribute) Unique ID assigned to the

Read More »

Agent Payload

Parent Cardinality Name Type Description Lookup Agent 1 ID Integer (Attribute) Unique ID assigned to the Agent Agent 1 LastUpdated DateTime (Attribute) The date agent

Read More »

OfficeDetails Payload

Parent Cardinality Name Type Description Lookup OfficeDetails 1 Name String The name of the Office OfficeDetails 1 ID Integer Unique ID assigned to the Office

Read More »

Office Payload

Parent Cardinality Name Type Description Lookup Office 1 ID Integer Unique ID assigned to the office Office 1 Last Updated DateTime The date the office

Read More »