SOW - "My lists" editing columns not working

[Vlad7]

We are having an issue with the "My lists" in Service Operations Workspace.
When a user tries to "Edit Columns" on one of his/hers list by removing or adding any of the fields.
The list does not get updated with those changes. This only happens with older lists.

If they do create a new list user is able to edit those columns.

When I open the list in "sys_ux_my_list", I get the alert "GlideTransaction is not allowed in scoped applications".
Checking the logs this points to the "Duplicate UX My List Record" Business Rule. Which has not been modified.

I've checked with Access Analyzer and the user does have the permissions to edit the list but it doesn't work.

[MaAhyelL]

Hello, may I know what was the resolution for this issue please? 

[BurtCrepeault]

In my case, the KB article was not the cause of the problem.

Rather, Itil users in SOW can copy/create lists, but once defined, the save option on the list appears in certains cases but not others. For example, if they change columns (placement, width, list of colomns), the changes can't be saved and the list resets to default when they leave and come back. However, changes to filters can be saved. I don't know if this is by design, but it's surprising that one type of change can be saved but not the other.

I do have a message when I go to the user's sys_ux_my_list record, but I'm not working in a scope, so I don't know why that's there.

[Johan van den H]

We are also experiencing this issue in My Lists in Service Operations Workspace.

If you make a change to the list's filter you can save the change by clicking the three dots just right to the list name on the left of the page followed by Save.

Changes made to the columns are not being saved like that (not even if I also make a change to the filter).

I think this is a ServiceNow issue, as it also does not work on my PDI so I created a case for ServiceNow support.

[Johan van den H]

ServiceNow support answered that this is a bug which will be addressed in the Yokohama release.

The reported issue is marked as product bug PRB1798031 and The PRB PRB1798031 is marked as "Fixed" because this issue has been fixed in the Yokohama release.

Most Probable Cause:
PRB1798031 - 'Edit columns functionality is not working as expected in configurable workspace'

[Johan van den H]

We have rejected this solution, as it is not solving the issue we are facing now on our Xanadu instance.
It might help if other people that experience this issue create a case for ServiceNow support, so th issue gets more attention.