- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 01:54 PM
We have an instance on Utah Patch 1, using list v2, and the Personalize List Columns slush bucket is not working as expected.
Steps to reproduce:
1. Select the Personalize List (gear icon), add new columns to the "Selected" and hit OK. Nothing happens, the columns do not change.
2. Enter cache.do in the Filter Nav and then navigate back to the previous table. The columns are updated and the columns from step 1 are displayed.
3. Add or remove columns.
4. Nothing happens on list view until cache.do is ran again.
This appears to be on all tables. The user can't personalize the list columns without running cache.do to reflect their changes each time.
Anyone know why this is and how to fix it?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2023 06:08 AM
Support was able to provide a solution.
"This has been identified as a bug and reported to the development team via PRB1639538 and the workaround would be to navigate to the sys_language table and search for English and take an export and in the XML change the value of the field Active to true. and reimport in the instance. Which will fix the issue."
That worked for me. Hopefully it helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2023 02:09 AM
Exactly the same situation here, have to clear the server cache to get any additional columns to display. Am going to upgrade to Utah Patch 1a today to see if that makes a difference.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2023 03:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2023 06:08 AM
Support was able to provide a solution.
"This has been identified as a bug and reported to the development team via PRB1639538 and the workaround would be to navigate to the sys_language table and search for English and take an export and in the XML change the value of the field Active to true. and reimport in the instance. Which will fix the issue."
That worked for me. Hopefully it helps.