When attempting to add extended fields of cmdb_ci (and possibly other Table Per Partition) fields, large table structures can cause adding those fields to be unacceptably slow, and potentially locking the browser. This is likely to occur in any place where you are able to add extended fields using a slushbucket, such as in the Report Builder or when trying to add dot-walked fields to forms configuring Form Layout.
Steps to Reproduce
Note – These steps are valid for user interfaces prior to UI16. Although the issue does occur on UI16, reproducing it on that UI requires slightly different steps. if you get switched to UI16, click the gear icon in the upper right and switch to UI15.
Go to /sys_properties_list.do and set glide.ui.list.allow_extended_fields sys_property to true.
Go to sys_report_template.do.
From the Data drop-down menu, select Table > Task (or any table that has a reference to the Configuration Item table).
In the list of Available fields, scroll to find the Configuration Item field (or whatever field references cmdb_ci) and click it.
Between the Available and Selected fields, a new "mapping" icon appears above the < and > icons.
Click the new icon.
Expected behavior: Available fields will be updated to show all of the fields that extend from the cmdb_ci table. This should take a reasonable period of time.
Actual behavior: The browser locks. Although the browser will eventually become active again, its return takes an unacceptable period of time.
There is no effective workaround for this issue. Since the issue only appears when the glide.ui.list.allow_extended_fields property is set to true and therefore if the fields aren't needed setting this to false is a potential, but limiting workaround as the if the extended fields are required then those will not be listed or available for the report.
Some customers have observed that Firefox performs better when the very large payload is returned from the server, so that it's just very slow, rather than crashing. Firefox might be a temporary workaround for some customers.
Upgrading the software to a fixed version (JP6 or JP5 HF2) is the only way to get the report builder working the way the customer expects.
When an instance is already on a version that contains the fix and the "old reporting UI" is being used, the report would need to be re-created to see the fix take effect.
Alternatively, you can use the "new report UI", which will avoid this issue altogether.
Related Problem: PRB1169930