[sync-services-developers] Record Pushing Issue

[Jud Spencer]

On 11/22/05 8:07:02 AM, "Brian M. Criscuolo" <bcriscuolo at markspace.com>
wrote:

> Is it because I'm accepting all addresses when pulling the original
> record but only providing a subset of them when pushing a change
> back, as outlined above? Did Apple change the behavior of:
> "SyncSession should not issue a "clear" for Q." but not document it?
> 
> There were numerous Sync Services changes in 10.4.3 but none were
> described in any detail. We need some detail about them, as shipping
> code behaves differently.
> 
> Does anyone have any thoughts or suggestions to this perplexing issue?

I'm new to the sync services game. I essentially started with 10.4.3. I have
found that in a case where you are pushing a subset of entities related to a
parent, that you need to provide the ID's of all the sub-entities in the
parent, not just the ones that are being pushed. What we are doing in our
app is keeping track of the entities when we have a schema incompatibility,
and then pushing them on any update. For example, our app only supports two
addresses. When we pull a record with more than two, we keep track of the
ids of the ones that we accepted but didn't write to our database. When we
later push the record back to the truth, we write the id's of the addresses
that we write as well as the ids of the ones that we don't write into the
street addresses property in .Contact.

This works for us.

Jud