@Robert Cebula Thank you for submitting your question.

If you manually start a sync (by clicking Start Full Sync), iiQ will pull in data. 

Push Data = This will take the data from iiQ and only push it into Google Devices

Multiple different data fields can be written back from iiQ to Google Devices. 

1. The following device actions can be written back to Google Device = Deprovision Device, Disable Device, Enable Device, and Wipe Device 

    

2. The following field can be written back from iiQ to Google Devices = Annotated Location, Annotated User, Annotated Asset ID, and Notes
3. Write orgUnitPath to Google:  This option allows iiQ to update a device’s OrgUnit path(s) in Google Admin Console based on any criteria supported via iiQ filtering conditions (e.g. Role, Grade, Location, Model, etc.).

I hope this information helps! 

So if I unassign the chromebook in iiQ and manually start a sync shouldn’t it push the unassignment of the owner to the AnnotedUser field in Google (i.e. blank out the field in Google)?

@Robert Cebula Do you have an example of an asset tag I can look up?

CDVKX23

@Robert Cebula Did you reauthenticate when you turned on the Google Device writeback option? If you did not, this may be a reason it is not updating the metadata from Google. 

My apologies, it looks like it is actually updating the metadata from Google, there is just a delay even after the sync completes.

@Robert Cebula Glad to hear it. Please direct your questions to your implementation specialist until you go live! Thanks!