@jclark Thank you for submitting your question to our community!

I am looking into this, but I have reached out for some additional assistance. Did you submit a support ticket on this? If so, what is the ticket number? 

I did not, because I’m assuming this is how it was designed - that’s usually the answer I get lol.

I am looking into a workaround right now, but still curious is that’s expected behavior or not.

@jclark It was confirmed this is functioning as intended—however, a possible workaround. If you uncheck the updated asset, you will be given the update custom field option to select. This will update only the custom field instead of the asset tag. I hope this helps. 

@jclark what do you have in your Data Mapping set to for the Asset Tag?

I did not, because I’m assuming this is how it was designed - that’s usually the answer I get lol.

I am looking into a workaround right now, but still curious is that’s expected behavior or not.

@jclark what do you have in your Data Mapping set to for the Asset Tag?

 

@akorkishko 

Since we have several connections for assets (Jamf, Google, Intune, SCCM) we don’t have anything set there. That just chooses an app that takes first priority when mapping, but doesn’t stop it otherwise.

@jclark It was confirmed this is functioning as intended—however, a possible workaround. If you uncheck the updated asset, you will be given the update custom field option to select. This will update only the custom field instead of the asset tag. I hope this helps. 

 

@Kathryn Carter I appreciate the response - I did state originally that we were doing that previously, but none of the metadata was being updated that way. It doesn’t make sense to me that there’s no way to stop the device name from mapping to the asset tag field, and it’s also not documented anywhere.

As a workaround, we are going to try mapping the asset tags to the “ManagedDeviceName” in Intune, which is a separate field from the “Device Name”. This is going to take some time, though.

@jclark Yes I understand how this would be confusing. Please let me know if adjusting the name mapping helps! 

@Kathryn Carter circling back to this - as I’ve still hit a dead end.

• If we leave “Update Asset” unchecked - all of the meta information from Intune is immediately stale the next day, so it’s pointless to have it. (recent users, etc. We need all of that.)
• If we leave it checked - the “Device Name” writes to the asset tag field in iiQ by default.
• The only field iiQ can write back to in Intune is the “Managed Device Name”, so we tried a “both directions” sync, mapping that to the asset tag field in iiQ. Set our asset tags in iiQ and run the sync… It does a “pull” from Intune first, before a “push”… so it’s taking whatever the current value is in Intune, writing it to the asset tag field in iiQ, and then pushing that same value back to Intune (which is absolutely pointless).
• I really don’t understand why this is the way it is. We basically have to choose between keeping the asset data up to date, or having an asset tag.

I have to be missing something...

@jclark I am confused.

“It does a “pull” from Intune first, before a “push””

Is this happening in a manual sync or the nightly sync? The data should be pushed and then pulled. If it is the nightly sync, let’s get this escalated to support. 

From a manual sync - is the behavior not the same if I click the button versus it running itself overnight?

I haven’t tried to see if it’s different with the nightly, but… If that’s the case - I honestly can’t make a single change and wait an entire day to see if it worked overnight before trying the next thing. That’s awful. lol

A “Push changes to Intune” action would help here - similar to Google!

@jclark So when you perform a manual sync, you will need to push changes first before the sync. That would be the main issue here. I agree a Push changes to intune action would be great, I have created that idea for you here: 

@Kathryn Carter thanks for creating that, and thanks for the assistance!

Stumbled across this post as we have a similar issue. I think that if under the Asset Field Mappings we could select “Incident IQ” as the Preferred App for Asset tags as this is a headache for custom fields and write backs to any system other than Google. I leave it set to Google because SCCM/Intune/Mosyle are unreliable. (and not updated by me)

@JustinC I would suggest leaving your MDM for your “source of truth” where no one is touching those asset tags with the assets to keep one correct record.