Loading...
Loading...
Running a report that includes many variables on many tables causes the SQL Exception "Unknown column 'sc_item_option.value' in 'field list'". Each inclusion of a variable, in either a report or query, results in the creation of an SQL join term in the resultant query. If the variable is of type "Reference", it would also need to JOIN to another table to get the result. Due to this, even though this particular KB lists the high-end limit of 60, we have found it to be closer to 25 in past cases.
Navigate to Reports > Create New. Select the Data table "Requested Item [sc_req_item]". Customize the columns by selecting Variables in the Columns Available. Click the + sign that appears above the < and > arrows. In the Catalog Items window, search for and select 'DG - Data Quality Issue Form'. Select and add all the variables for DG - Data Quality Issue Form (approximately 75 variables). URL: / item_option_new_list.do?sysparm_query=cat_item!%3DNULL%5EGOTOcat_item.nameLIKEDG%5Ecat_item%3Dcce6f898ac327100aca2265fc8d82cdf%5Eactive%3Dtrue Add a condition so fewer records are retrieved, for example, opened by 'Guest'. Run the report. Message is shown: "Syntax Error or Access Rule Violation detected by database (Unknown column 'sc_item_option.value' in 'field list')".
After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Technical Support. Perhaps this workaround can provide temporary relief: Split the number of variables displayed across multiple reports ensuring that the number of variables displayed does not exceed the limit, for each individual report. Note: 1 variable = 1 join
PRB675410
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.