Difference between configuration_item and cmdb_ci on sc_req_item table

[Mandy11]

Hello everyone,
Can you explain to me why we have 2 fields for the CIs in the table sc_req_item. I see that cmdb_ci field is inherited from task table. We use the field configuration_item from sc_req_item table.
For what reason ? Why don't we use the same field as the other tables (incident, problem, change) ?

Thanks

[Community Alums · Accepted solution]

HI Mandy,

This is what @Joe McCarty  has to say from ServiceNow:

One con to the cmdb_ci field is that it can trigger affected ci notifications.   While useful on incidents, problems and change, it may be annoying to receive affected CI notifications every time someone requests access if the application is listed as the CI or other routine requests.

Of course macro reporting across multiple task types on CI is hampered by request item using a separate CI field (i.e. 2 CI fields makes doing a group by on CI a problem).

But if I'm not mistaken, configuration_item is what is on the sc_req_item form OOB.   All things being equal, I would leave it as is.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep