- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2024 09:00 AM
We have three instances on Washington DC with Next experience. In two of them (prod and test) we are experiencing an issue where Next experience is not loading for some tables, but loads fine for other tables. Instead an older version of the UI appears. Our dev instance does not have this problem at all.
Some examples of tables where the Next experience is NOT loading: sc_task, sys_user_group, sc_cat_item, sys_properties, syslog. This is what it looks like (note the new button is on the left, like with the previous version of the UI before Next experience):
Some examples of tables where it is loading fine, in the same instances: sys_user, sys_email, sys_update_set. This is what it looks like (note the new button is on the right like is expected with Next experience):
Those same tables which aren't working in the two instances work fine in the third (dev). There's no difference in URL other than the instance name.
Does anyone know why the Next experience UI does not seem to be loading for a subset of tables in some of our instances?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2024 11:49 AM
We opened a HI case for this and learned that the system property glide.ui.list_v3.enable was causing this behavior on some tables. This is a legacy property that is false on new instances. Both of our instances that had the problem had this property set to true. We set it to false, and the issue was fixed.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-20-2024 05:43 AM
I'd open a case for this one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2024 11:49 AM
We opened a HI case for this and learned that the system property glide.ui.list_v3.enable was causing this behavior on some tables. This is a legacy property that is false on new instances. Both of our instances that had the problem had this property set to true. We set it to false, and the issue was fixed.