Two configuration item fields in sc_req_item tableIssue There are two fields for the configuration item at the sc_req_item table level. One is on the TASK table, the other was additionally included in the "sc_req_item" table level. https://<<instance_name>>.service-now.com/sys_dictionary_list.do?sysparm_query=name%3Dsc_req_item%5EORname%3Dtask%5Ereference%3Dcmdb_ci&sysparm_view= CauseOn sc_req_item table there are two fields with the name Configuration Item (cmdb_ci, configuration_item).cmdb_ci is a field that is inherited from the task table and it is dependent on "company" as per out-of-box (OOB) configuration. This field is synced with the affected CI ("task_ci") table by the BR "Sync CI with Affected CIs.".https://***instancename***.service-now.com/nav_to.do?uri=sys_script.do?sys_id=6f8daf204a3623120146c79f308310dfconfiguration_item is a field on sc_req_item that is not dependent on company. The purpose of this field is to show only the configuration items whose status is "In Stock" as per OOB configuration. So, by design configuration_item is not synced with the affected CI.If you want configuration_item to be synced you can write a business rule similar to "Sync CI with Affected CIs."ResolutionThe usage of the field is a business decision but the below points can be taken into consideration before making this decision. OOB sc_req_item uses "configuration_item" which is considered the best practice and we encourage you to leave it as it is.Using "cmdb_ci" is not an issue but it may trigger additional CI notifications that are more useful on incident vs requested item table.One con to the cmdb_ci field is that it can trigger affected CI notifications. While useful for incidents, problems, and changes, 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. Some examples of the usage of the Configuration Item and CMBD_CI are listed below: Use the configuration item when someone orders a laptop and it will populate in the configuration item.For example, suppose a load-balancer in a data center is no longer operational. The Configuration Item field lists the specific server which is out of memory. The Affected CI-related list contains the load-balancer, the data center, the servers that depend on the load-balancer, and business services that are impacted by the missing server.Another example: Let's say you have an incident with a broken router in your environment.You may want to specify the router as the main configuration item that is involved in the incident.Yet, in the affected CI list, you may need to put any switches or servers that are using this router that may be impacted as well.