Best Practice for setting up assets across multiple locations

Userlevel 1
Badge +1

I see there’s no way to have custom fields for Locations, so what’s the best practice for showing what systems are running at different locations.  E.g. 100 sites run SystemA, 50 sites run SystemB, 50 sites run SystemC.  We have 2000 users across all these sites.  So, if I build all 200 sites as locations, do I have to build 100 of the same exact software asset in the Inventory object and then assign all 100 to an individual site?  That feels extremely inefficient so I have to be missing something somewhere.  There has to be a way to build a single asset, assign it to multiple locations, and then assign users to those locations (Right??  Someone please say “yes!”).  

0 replies

Join the Community or User Group to Participate in this Discussion