@LREAGOR 54388e3 sville Thank you for submitting your question. 

I appreciate your patience for a reply. I would suggest doing a bulk import with updated information. You will not have to delete the devices, but you can update the information in bulk via import. Please let me know if this is what you are looking for. 

Here is a guide to importing the information for your devices.  

Unfortunately, an import doesn’t update the type shown in the device record. Here’s a video showing that process.

https://drive.google.com/file/d/1m-6eOsAU2ZqROnIx3O_-d9IdGWot0a7y/view?usp=sharing

You can see that the device type continues to show the old type until I edit and save the record. The only way we have to do this in mass is to delete them all and then reimport them.

It seems like this is a bug and it should update in the device record once the device type has been changed for the model.

@LREAGOR 54388e3 sville I spoke with one of my managers, and he suggested updating the asset type on the model, and then you can bulk update the model via import, and all the information (asset type and model) should match your devices! 

I did that. You can see in the video that the device record still showed the old Asset Type after the import. It took an edit and save to get the record to show the new Device Type.

I’m guessing that the import is doing nothing since the Model isn’t changing. For the import method to work, I guess I’ll have to actually change the model to a different model, then change it back to the correct one via the import.

@LREAGOR 54388e3 sville Okay, I am following now. I don’t think I have had enough coffee yet!

Please submit a ticket to iiQ support for this issue. This needs to be escalated to that team; I appreciate your patience. 

@LREAGOR 54388e3 sville I found an open ticket within our data base - I will add your information to the ticket. 

Thanks, Kathryn!

Kathryn, we had this issue come up again today. I wanted to check and see if you can tell if anything has been done with the ticket concerning this issue. Also, is there a way that I can see the status of this ticket?

@LREAGOR 54388e3 sville This was created in our internal ticketing. I checked on it, and it looks like the fix should be deployed soon! I will update you when this fix officially goes live