[sync-services-developers] Record Pushing Issue

[Brian M. Criscuolo]

Hey everyone,

I'm running across a really strange issue that did not happen on  
10.4.2, but now does on 10.4.3.

When I push records from a device (Palm) into the truth, I don't  
necessarily have *all* the data that makes up an entity. For  
instance, the Palm address book only supports three street address  
fields. That is all I can push. If the truth contains 5 street  
addresses, three of them are reflected on the device.

Previously, I would push the street address record containing the  
changes into the truth and whatever change would be merged in  
(updating one of the 5 records, for example).   After the sync, all  
five records existed in the truth with the changes pushed.

Now, on 10.4.3, if I only push three records, the other two records  
are DELETED! This is a change from the previously existing behavior,  
and I'm not sure why.

Does this statement have anything to do with it?
"ISyncSession can push "clear" deltas for properties that were added  
when a client accepted a record but did not subsequently provide. For  
example, if a client accepts record A and adds a property Q in the  
formatted record, then pushes a change to X that does not include Q,  
ISyncSession should not issue a "clear" for Q."
<http://developer.apple.com/releasenotes/AppleApplications/ 
SyncServices.html>

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?

Thanks,
b

********************
Brian M. Criscuolo
Senior Software Engineer
Mark/Space, Inc.
bcriscuolo at markspace.com
<http://www.markspace.com>