Meraki integration is only creating CIs - no assets are created

[bjmcdonald]

We are experiencing an issue where assets are not being created due to two conflicting model categories. 

We have a manually created model category called "IP Camera" with the asset class "alm_hardware".
During the Utah upgrade in September 2023, a new model category called "Cameras" (for which the ASSET is some sort of facility asset that we don't use) was created by the system.  Since the creation of "Cameras", CIs created through the Meraki Service Graph Connector have not been able to create assets.

How do we fix this?  Do we delete the system-created model category "Cameras"? We ideally want to continue to have IP Cameras assets to be created in alm_hardware.  

[AJ-TechTrek]

Hi @bjmcdonald ,

Basically, You should use the OOB model Category but you are already created a Model category and using the Same , hence there is no issue continue with the IP Cameras Model Category to create the Asset.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[bjmcdonald]

My question is this - WHY were these model categories (we found 70+ model categories that we do NOT use) from Enterprise Asset included in our Upgrade - when we don't use Enterprise Asset module?  Has anyone else found this ?