Custom CMDB table naming standards

[pbels1]

In the CMDB Data Foundations there a KPI for custom table naming standard and in the Service Now Health there is a mesurement for custom table that are not part of an application.  I have tried to create a custome CMDB table with in a application using class manager and the genterated a name with the application inforamtion example `x_144954_cmdb_ex_0_cmdb_ci_server_appliance`.  This seem like it would cause an issue on the CMDB Data Foundations but not the Service Now Health.  But if I create the table in the global application I get the name `u_cmdb_ci_server_appliance` which will pass CMDB Data Foundations but in Service Now Health it will so as an error for a custom table with no application.

How can a custom CMDB Table be created that will pass both checks?

[Sandeep90]

@pbels1 Can you explain more what issue you are encountering in service now health, it should not cause any issues as long as the table is created correctly, meaning it follows the hierarchy of cmdb_ci. 

[pbels1]

In the service now health scan we are getting message of custom table not in an application.  An example of this is u_axp_cmdb_ci_mainframe_job.  This will also show an and error in the CMDB Data Foundations report because it does not follow the u_cmdb_ci, this naming convention has been used since Aspen.  I am trying figure what we can rectify these errors so it can be satisfied by both scans.

[Sandeep90]

@pbels1 Not sure which report you are mentioning but afaik there is no such restriction on table name that you provided in CMDB Health dashboard.