@JWindell 960ef7a roundrockisd Great question!

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

Start Full Sync - This will sync all data between iiQ and Google Devices to update assets between the two so they will match! 

I will be updating our guide to match the information I have provided 

Thank you, Kathryn!

Which order happens first? If I check in a computer in iiQ I have it clearing out the user, when the full daily sync happens it adds the user back since in Google it’s still there but keeps it in the “in storage” status. 
 

Im brand new to iiQ we are still in onboarding and I want to make sure I’m not running things wrong. 
 

Yesterday after changing some asset tags and checking in a few computers I manually pushed. Is there a way to set the priority for which way goes first?

I would also like to know which data source takes priority. If they don’t match, it seems like Google’s data wins when doing a full sync.

Can this be changed to be the opposite? We would prefer to only update one datasource, iiQ.

^

@FGonzales 4306de6 pausd @MMaitner 190651a ewsd @calexander 

We allow districts to determine which solution is the source of truth for data via more granular controls in the apps that support write-back functionality - it’s not always either iiQ or the product we’re integrating with that’s the "source of truth.” We should look at the integration first; make sure you enable the write-back functions! Here is one of the guides that explain the write-back features we offer:

If you manually start a sync (by clicking Start Full Sync), iiQ will push any change first and then will pull in data. This happens the same way with the nightly sync. 

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

There are multiple different data fields that 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.).

@FGonzales 4306de6 pausd 

The asset status will change to “In Storage” if you are checking in a device. You are able to change this by setting up a rule when an asset is checked in. 
Regarding “adds the user back since in Google it’s still there” - Is is happening because you have the following setting enabled for Google Device: 

Push Data needs to be a Permission we can TURN off for Agents.

@etan Thank you for your comment. Would you elaborate on your use case here? 

I was troubleshooting the google sync and I go to sync history and I notice a TON of push data syncs by our librarians who have low level agent access. It was hard finding the sync history I need to check (full sync). There is zero reason for our librarian agents to click the push data button, no one has told them what it is or what it does and yet they’re clicking it.

@etan That makes sense. Thank you for adding to your comment. That would be an enhancement to our permissions. Would you comment your idea on this idea: