Loading...
Loading...
This known error combines fixes for the related defects listed in the table below. The highlighted cells indicate that a combined workaround update set is available and attached to this article: Found/Fixed ❌ = Broken in this release ✅ = Fixed in this release ❌ = Fixed with workaround Problem
SDP9 SDP10 TP4 TP5 TP6 TP7 UP0 PRB1623594 With Next Experience enabled, list editing in a grouped list displays the incorrect cell editor ❌ ✅ ❌ ❌ ✅ ✅ ✅ With Next Experience enabled, grouped list column headers misaligned ✅ ✅ ❌ ❌ ✅ ✅ ✅ PRB1641058/KB1270814 With Next Experience enabled, list editing in a grouped list displays the incorrect cell editor when list actions are hidden ✅ ❌ ✅ ✅ ❌ ✅ ❌* Grouped list editing on dashboards ✅ ❌ ✅ ✅ ❌ ✅ ❌* PRB1630973/KB1289138 With Next Experience enabled, list columns headers are misaligned when list actions are hidden ✅ ❌ ✅ ✅ ❌ ❌ ✅ With Next Experience enabled, grouped list column headers are misaligned when list actions are hidden ✅ ❌ ❌ ❌ ❌ ❌ ✅ PRB1595333 With Next Experience enabled, list "Select All" checkbox is missing when list mechanic is hidden ❌ ✅ ✅ ✅ ✅ ✅ ✅ PRB1615740 With Next Experience enabled, list columns and headers are misaligned when expanding 'Group by' in list report and list view ❌ ✅ ❌ ❌ ✅ ✅ ✅
Log in to an instance on any of the Impacted versions mentioned above. Go to any list (example incident.list). Click on any field context menu and select Group By <field name>. Expand the group results. On any record, double-click on any field value to update. The box that pops up pulls data from the column to its left instead of the selected field value. The cell editor of the selected field should be displayed, but the wrong cell editor is displayed instead. It opens the cell editor of its left column.
The problem has been fixed. If you are able to upgrade, please take a look at the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. Meanwhile, you can apply/use any one of the workarounds given below. Application steps Steps to rollback workaround after upgrade Workaround option 1 Clicking any grouped row heading will take you to a list of items for only that group. Shift+Click on that row link to open the list in a new window. Do the list edit in the non-grouped list. Nothing to rollback Workaround option 2 Set the instance to work on the classic mode (U16). Set the property: glide.ui.polaris.experience = false Re-enable polaris experience Set the property: glide.ui.polaris.experience = true Workaround option 3 Disable Polaris for only affected users. This will be less disruptive to all users. Create a sys_user_preference for each user: name: glide.ui.polaris.use value: false Remove the sys_user_preference records where glide.ui.polaris.use = false and system = false Workaround option 4 Note: This is the less recommended option and make sure to rollback once upgraded to a fixed version if applied. Follow the 'load an update set' PowerPoint to load the respective attached update set based on your affected instance version. Use 'Accept remote' for any errors (there are action links in each of the list items for the updated ui macros and ui scripts). These files are attached to the KB/PRB. Rollback the update set. A workaround update set for Utah Patch 0 is available in PRB1641058/KB1270814
PRB1623594
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.