Loading...
Loading...
There are no known steps to reproduce as this is a complex instance specific problem.
This problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. 1. Disable Filtering “Excluded Relations” from Relationship Formatter: By default, Relationship Formatter excludes all the relationships specified in “cmdb_rel_filter” table. However, this can in some cases result in more DB queries being done to fetch the data for Relationship Formatter, impacting performance. In order to disable this, system property glide.cmdb.relation.filter can be set to false. 2. Another workaround to prevent the issue is to set the system property glide.ui.max_relations to 100 or 200, changing its default higher value 1000, and to set the default relation levels to 1 or 2. Create a new “User Preference” record to manage the default number of relationship levels fetched. Go to left nav -> User Preference -> New Fill out the form per the attached screenshot Set the depth value to 1 or 2 as needed Save Example: If there is a large number of orphan relationships, contact Technical Support for them to be found and removed from the database via an internal script.
PRB1412232
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.