Asset Tables with prefix sn_ent_

[David77]

We have almost 40 tables with the prefix: sn_ent_ in our system. 

What created them/what application or plug-in?

What are they for (this old post does not mention them https://www.servicenow.com/community/now-platform-articles/the-meaning-of-cryptic-table-prefixes-and...)?

Some of them interfere with user defined Labels we've already created which reference alm_hardware, what is the best way to deal with this?

Thanks!

[Jitendra Diwak1]

Hi @David77, 

Tables with the prefix "sn_ent_" are typically created by ServiceNow Enterprise Management. They are part of the Enterprise plugin suite and are used for various IT operations management functions such as asset management, configuration management, and service mapping.

These tables might interfere with user-defined labels referencing "alm_hardware" if there are conflicts in naming or if there are dependencies between these tables and the labels. To deal with this, you could consider:

1. **Renaming conflicts:** If there are conflicts in naming between the user-defined labels and the "sn_ent_" tables, you might need to rename either the labels or the affected tables to avoid conflicts.

2. **Dependency management:** Identify any dependencies between the user-defined labels and the "sn_ent_" tables. Depending on the nature of these dependencies, you might need to adjust configurations or workflows to accommodate both without interference.

3. **Customization:** If possible, customize the behavior of the "sn_ent_" tables or the user-defined labels to better align with your organization's requirements and to minimize conflicts.

4. **Documentation and communication:** Ensure that stakeholders are aware of the potential conflicts and how they are being addressed. Document any changes or configurations made to mitigate these conflicts for future reference.

By carefully managing naming conventions, dependencies, and configurations, you can minimize conflicts between user-defined labels and "sn_ent_" tables within your ServiceNow instance.

Please accept my solution if it resolves your issue and thumps 👍 up 

Thanks 

Jitendra 

[David77]

Jitendra, thanks for the quick response!  So, I checked and we do have this installed
"Expanded Model and Asset Classes"

If we wanted to use option 1, rename conflicts, do you have any recommendations as to how to proceed, as my concen is that if we rename anything that a later update from SErviceNow won't reinstate the name. 

For example, we had previously created a user-defined model category "AV Equipment" pointing to alm_hardware and u_cmdb_ci_av_equipment. 
However, this update also created model category "AV Equipment" pointing to
sn_ent_facility_asset and cmdb_ci_multimedia. 

Thanks!

[Robbie]

Hi @David77,

Are you aware if the following application / plugin has been installed on your instance:

https://store.servicenow.com/sn_appstore_store.do#!/store/application/7e67d4ff091b4110f87739da6a8d8c...

"The Expanded Model and Asset Classes app is the single source for all new, out-of-the-box, expanded model classes, asset classes, and model categories defined by ServiceNow"

New Tables:

• New Product Model class Medical Device model [sn_ent_medical_device_model] added as an extension of Medical model [sn_ent_medical_model].
• Add “allow_alt_maintenance” column with data type as boolean to sn_ent_model table.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.

Thanks, Robbie

[David77]

Robbie, thanks, and I confirmed we do have "Expanded Model and Asset Classes" installed, as you suspected. 
I posted a question above as to how to work around this without having to uninstall this.