​@AWilson 61044d5 shawneeps  Thank you for submitting your question!

Models and Model Categories that the source is Incident IQ Catalog cannot be modified other than their product visibility. 

Custom Models and Model Categories can be modified as you mentioned. I would suggest creating custom models and model categories for those Incident IQ Catalog created ones that are in read only. Additionally you can then turn off the visibility (disable) for those so only the custom created ones are visible.

Does that answer your question?

Thank you!

​@LWoods_iiQ I just recently got off a call with Mike Lund our customer success manager and he advised we shouldn’t create duplicates but I was thinking the same thing.

​@AWilson 61044d5 shawneeps That’s awesome that you were able to connect with your CSM! ​@MLund_iiQ  is awesome!

We discussed and agreed that there are some warnings that to be aware of when duplicating model categories, especially if you already have model categories that exist within conditions of rules. Those will need to be updated to the custom model categories and make sure you are choosing the same ones. We discovered that if you search for model categories, all categories show whether they are visible or not (see screenshot). My suggestion would be to label accordingly to aide in eliminating any confusion.

It is still a recommended solution to accomplish your request, but also realize there are some specific items to pay close attention to when doing so.

Hope this clarifies! Thanks!

So your advice is to go ahead and create duplicate model categories?

One thing I thought about was to change the model mappings but they are missing. Which is the issue that sparked this discussion. I’m importing from FileWave and FileWave imports the models as iPad 1,1, iPad 1,2 iPad 11,6….etc. All of these models disappeared from the mappings but the models are still present in the system.

But other ipads cannot sync without the model mappings.

Why did my model mappings disappear? How can I bring them back? If I mapped a custom field they comeback but all my other mappings disappear?

Please help!

I need a solution soon! We have over 2,000 ipads being skipped in sync because of this issue.

If it can’t be fixed through model mappings then how? Filewave’s meta data does not show the actual model of the iPad but only in this format: iPad 1,1. I have to associate that to an actual model type in IIQ. Should I just create models that match Filewave’s Product Name?

Please Help

​@AWilson 61044d5 shawneeps  I apologize for the delay in responding. Those ipads will need to be mapped under the Model Mappings in the Filewave app within iiQ. If the model does not exist then yes it will need to be created in iiQ for the app to know where to put the assets.

Click the create new model if it doesn’t exist in the dropdown menu when you click Unmapped.

Hope this helps! If you need additional assistance let me know!
 

Thanks!

Hi Leann,

Thank you so much for replying.

So we have different models of ipads but they all seem to fall under “iPad” in the model mappings.

This was not the case at one time. I mapped all the various model iPads to actual models like iPad Generation 1 and such.

I’m already aware of the solution you provided above. If I do that every ipad will be the same model even though we have multiple models.

Hope you understand what I’m saying

​@AWilson 61044d5 shawneeps Understood. Unfortunately I cannot see your FileWave asset models, but it is pulling the Asset Model from FileWave and then map to a model created in iiQ. Can you verify that all the models of iPads are created in FileWave? Similar to the different MacBook airs you see in the screenshot below?

There are models in IIQ but the mappings disappeared and I’m not sure why.

I believe IIQ is only looking at one field from the Filewave data which is “Device Product Name”. For iPads it only says iPad. In Filewave, “Product Name” and “Product” give the iPad models such as iPad 11,6 or iPad 8,5.

Something changed somewhere but I’m not sure. I noticed this after our FileWave server upgrade. This may be an API issue.

​@AWilson 61044d5 shawneeps I think you may be onto something.

I think so... IIQ needs to change how iPads are sync from FileWave. Instead of using “Device Product Name” use “Product Name” or “Product”. 

​@AWilson 61044d5 shawneeps I wonder if that is a custom value you can map from FileWave.

I would suggest to submit a support ticket and they may be able to assist you more than what I have access to.

Thank you!

It is a custom value! 

Every time I add it the other mappings disappear. Crazy!

Unless I’m doing it wrong.

​@AWilson 61044d5 shawneeps  It is likely because you are now pulling model mappings from a new field source in FileWave so everything will need to be remapped. Have you tried using the Auto-Map Models button in the top right? It should accurately map the majority of them saving you time.

So by adding the new custom fields I lose the others? Like the macbooks and PC’s?

Should I add the fields for the macbooks and PC’s in a similar way? That seems logical?

It sounds like I’m overwriting the default fields by adding custom fields...is that what is happening?

Ok, I think I understand? So If I add “Device Product Name” also than all mappings will come back.

That didn’t work

I think the issue is that all the devices in FileWave have “Device Product Name” in common. There isn’t another field in this program that all devices share for model information.

I still think this is an API issues and IIQ needs to re-consider how IOS devices are sync’d from FileWave.

​@AWilson 61044d5 shawneeps I still suggest submitting a support ticket as they may have a better solution.
 

Thanks!

I have a support ticket submitted! Hopefully we get this resolved.

I was on the phone with our IIQ reps and they showed me a picture of another customers config for FileWave integration and I’m getting different results. Except I don’t have “Update Asset” checked or “Update Custom Fields”

The reason we don’t check this option is because a lot of our data fields in FileWave are incorrect.

We are choosing to correct the data in IIQ.