"Configuration Item" field in Problem record does not list the entire "Configuration Item" List as simialr to the "Configuration Item" field in "Incident" formIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms "Configuration Item" lookup field in Problem record does not list the entire Configuration Item List as compared to the "Configuration Item" lookup field on Incident record. Release Any supported release. Cause The "Configuration Item" reference field on task table had dictionary override setup for Problem table to have additional reference qualifier and hence due to this additional reference qualifier, the cmdb_ci field on problem form fires below query, SELECT ... FROM cmdb cmdb0 WHERE cmdb0.`sys_class_path` LIKE '/!!%' AND cmdb0.`operational_status` NOT IN (6) /*...*/ But the cmdb_ci field lookup on incident form fires below query as there is no reference qualifier set, SELECT ... FROM cmdb cmdb0 WHERE cmdb0.`sys_class_path` LIKE '/!!%' /*...*/ This causes the difference between the "Configuration Item" lookup on Incident and Problem record. Resolution Review the dictionary override setup on "Configuration Item" field for "Problem" table and modify it as per the business requirement. Additional Information Dictionary override Reference Lookup field