How to import 'My Lists' from Agent workspace to Configurable Workspace

ThunderDev · ‎08-23-2023

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?

ThunderDev · ‎10-19-2023

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.

View solution in original post

Maik Skoddow · ‎08-23-2023

Hi @ThunderDev

what do you need a cross-scope priviledge for? For a single migration you can write a script and execute as an admin.

Maik

ThunderDev · ‎08-23-2023

Hey Maik,

Thanks for the fast reply!

I tried to run a background script to copy the records from (sys_aw_my_list) to (sys_ux_my_list) but since the two tables are in two different application scopes -- 'global' and '@servicenow/now-record-list-menu-connected' I recieved an error 'Security restricted: Create operation against 'sys_ux_my_list' from scope 'rhino.global' has been refused due to the table's cross-scope access policy'

Can you go into more details on the way you would go about this?

Oleskii_Top · ‎05-16-2024

Create migration script as Fix Script in "@servicenow/now-record-list-menu-connected" Scope. This will solve scope problems and allow My list migration without xml manipulation.

Z B · ‎10-19-2023

I'm looking for the same.
Only idea I got was a manual export of sys_aw_my_list, editing the XML to change the <sys_aw_my_list> for <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.
Maybe a transform map could be done to aid it if needed for multiple records.