- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2023 05:51 AM
We are making a switch from Agent Workspace to Configurable Workspace. We have a lot of users that have created several lists inside 'My Lists' (sys_aw_my_list) in Agent Workspace. We want to move those over into 'My Lists' (sys_ux_my_list) in Configurable Workspace.
I tried to create a script to accomplish this but the sys_ux_my_list is in a private scope "@servicenow/now-record-list-menu-connected". Therefore I cannot add cross-scope policy to the application and I cannot select the table from the dropdown.
Is there any way to accomplish this without having to either manually as an admin, impersonate each user and re-create the list or have the users manually re-create the lists inside configurable workspace?
Solved! Go to Solution.
- Labels:
-
Workspace : Next Experience
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2023 05:01 AM - edited 05-08-2024 06:17 AM
Hello ZB,
That is what I ended up doing. I manually exported the sys_aw_my_list and then edited the XML, changing the table name from <sys_aw_my_list> to <sys_ux_my_list> and removing the sys_id value so there's no duplicates and system will assign new sys_id on import to sys_ux_my_list table. After that I just imported the XML file with those changes/
This worked for me and we didn't see any issues after doing this. I did reach out to SN Support and they wouldn't recommend this and instead recommend to manually remake the list inside the new table.
In our situation, this saved a lot of time and energy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2024 11:51 AM
Hello all. I agree with a previous poster that manually updating the XML invites error, although it is a potentially workable solution.
Instead, I created a Fix Script (written in the same scope as the My UX List (sys_ux_my_list) table) to create the sys_ux_my_list records from existing sys_aw_my_list records, copying the following fields: columns, condition, order, table, title, sys_domain. To get the key sys_created_by field (and other sys fields) to copy, I used the suggestion by @Z B to use autoSysFields(false). Have to make sure those fields copy over because ServiceNow uses sys_created_by to apply "ownership" over the personalized list. That seemed to do the trick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2024 12:27 PM
Small update: had to also use setWorkflow(false) because the 'Order' field was not being set properly. If you inspect the 'before' BRs on this table, one of them sets the 'Order' field and that was interrupting my attempt to set it via script to whatever the user had set it to in the original legacy AW table. In reviewing the other BRs, there does not appear to be any risk in skipping them via setWorkflow(false) so I went with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2025 05:06 AM
@Jamie Stroud how did you switch to the application scope of "My UX List" table. Its showing me cant switch to this application scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2025 08:35 AM
Hello All,
I am also trying to migrate to My UX Lists but I am not able to switch the scope. @Jamie Stroud , I would need your guidance in how can we switch the private scoped application.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2025 01:14 PM
@Priyanka Jha1 @vDev I just checked on the instance where I created this Fix Script and you're right, I can no longer switch to this scope. But I was able to in Sep 2024 when I created it. Not sure what has changed since then.
