As per CSDM 4.0, should we not populate any data in 'Service' [cmdb_ci_service] table right?

Suggy
Giga Sage

As per CSDM 4.0, should we not populate any data in 'Service' [cmdb_ci_service] table I believe?

We have a new Vancoucer instance with Demo data loaded and I see there are many records in cmdb_ci_service table.

Is ServiceNow still using wrong Demo data? or am I missing something?

Suggy_1-1708523914837.png

 

 

1 ACCEPTED SOLUTION

SN_Marcel Horn
Tera Guru

Your statement is correct but keep the hierarchy in mind.
According the table hierarchy you´ll "see" all Business- / Technical Services / etc. in the [cmdb_ci_service] table. This is also true even if you using the correct Business Service table: [cmdb_ci_service_business]

 

Please use latest SN products like the SPM Service Builder or the Digital Portfolio Management Plugin to put your records into the new extended tables by default.

 

SN_MarcelHorn_0-1708527545040.png

 

View solution in original post

4 REPLIES 4

SN_Marcel Horn
Tera Guru

Your statement is correct but keep the hierarchy in mind.
According the table hierarchy you´ll "see" all Business- / Technical Services / etc. in the [cmdb_ci_service] table. This is also true even if you using the correct Business Service table: [cmdb_ci_service_business]

 

Please use latest SN products like the SPM Service Builder or the Digital Portfolio Management Plugin to put your records into the new extended tables by default.

 

SN_MarcelHorn_0-1708527545040.png

 

l337
Tera Expert

CSDM requires us to populate application services in either the cmdb_ci_service_auto table or the cmdb_ci_service_discovered table.

 

An important thing to note is that when a CI record is created in either the above tables, a CI record also gets created in the cmdb_ci_service table.

 

CI records can still be created in the cmdb_ci_service_auto table however, eventually you will need to use the button "Convert to Application Service" on the CI form to have it populated as an Application Service in the cmdb_ci_service_auto and cmdb_ci_service_discovered tables. If you go this route, the CI will still exist in the cmdb_ci_service_auto table.

 

If you convert a CI from the cmdb_ci_service_auto table, the CI created in the cmdb_ci_service_auto and cmdb_ci_service_discovered tables will be classified as Calculated Application Service CIs.

 

If you create an application service CI in either the cmdb_ci_service_auto or the cmdb_ci_service_discovered tables, they will be classified as Mapped Application Service CIs.

 

I found all this out through testing in Sandbox which I suggest you try.

There is a difference between Mapped vs Calculated Application Services, below are a few community forum links I saved as a favorite for reference.

 

Application Services: How to use them? 

Mapped application service? 

 

Thanks,

l337

This statement is wrong "CSDM requires us to populate application services in either the cmdb_ci_service_auto table"

 

Its just a parent table/dummy table. Nothing should be created directly on that table.

 

I got above response from ServiceNow when I raised a support ticket.

Hello Suggy,

 

If nothing should be created directly on the cmdb_ci_service_auto table why does ServiceNow allow us to create new Application Service records on that table? If it weren't allowed it should not be possible but it is possible.