@ashleyj Thanks for submitting your question. You can update your assets via CSV format with the proper models. I suggest submitting a support ticket to ensure everything is mapped correctly for your specific case, but you can update the ipads with an upload! 

Yes, we are having the same problem. We have two iPad models showing from FileWave “iPad” and “iPad3,2” I believe the ninth gens should be showing up as “iPad12,1” but that option isn’t there as a source from FileWave.

I looked at the fields being brought in from Filewave and it seems that changing the source from model to product should fix that issue.

Another issue with mapping data is the inability to map some fields from IIQ to Filewave custom fields. For instance it would be great for us to map PO number from IIQ to a FileWave custom fields like IIQ_PO.

@dburk I would suggest submitting a ticket with support for this. For the additional mapping, I would suggest submitting your idea to our Idea Exchange: https://community.incidentiq.com/ideas

Did this issue ever get resolved? I have the same issue with iPads. I can go ahead and updated them all with a CSV but then the next time I sync with FW it changes them back. I have tried mapping the suggestions but that will then mess up any of the computers, as the iPads and computers use two different fields for model mapping in Filewave. 

​@MPudenz 3105f88 winterset I wanted to chime in and offer a possible solution until this issue is fixed. You can update your models with your CSV and then turn off the option for FileWave to update your models under the “Data Mapping”tab.  

Erika Foxworth- Implementation Specialist

That is exactly how I have done it in the past. But once I purchase or add a new iPad to Filewave I need to the import the models in order for it to appear in iiQ. Then I am back in uploading the CSV files again. 

I’ve only used Jamf for iPad/Mac mappings, but do you mean the models listed on the left of the Model Mappings tab under Apps>Filewave don’t come through correctly and just show “iPad”? Or is Filewave reporting the specific model (ie: iPad 3,2) incorrectly?

This is a section of what we see from Jamf:

In Filewave it list the macOS device model numbers under Device Product Name while all the iOS device model numbers are listed under Product Name. I can choose in iiQ to map one or the other but can’t pick both. When I choose Device Product Name in iiQ for mapping all iOS devices come in a iPad, so I can only map them all as one. 

Here is what it looks like in iiQ for the FW App

Oh boy, I don’t like that one bit :(  I’m assuming you’ve tried Filewave Support to see if they could do anything?

Would mapping a custom field for the iPads or Macs help manage the models? I think you can filter assets based on custom fields. Doesn’t solve the core issue but might be a workaround.

There doesn’t seem to be a great work around at this point. Just running the sync then uploading the data via CSV. But once you get a new device and want it in iiQ you have to do the whole process over again. It works for now, was just double checking I wasn’t missing anything. Thank you!

​@MPudenz 3105f88 winterset I am bummed on your behalf!! At least now I know of this issue in case anyone in my professional circle asks about Filewave’s asset management though.