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

ThunderDev
Tera Guru

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? 

 

1 ACCEPTED SOLUTION

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

16 REPLIES 16

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.

Z B
Tera Contributor

Thank you for the update.

To leave it if someone else comes here. Instead of modifying XML which can be a lot of multiple records we can use easy import of excel file. We can choose which columns to include (or exclude sys_id in this case), then when transform map is prepared we need to add script to stop the system overwriting sys_created_by for admin. This will happen upon normal import of .xls and is unwanted as in this table sys_created_by decides whose list it is. 

Something in these lines would help: 

 

var userID = source.u_created_by;

target.autoSysFields(false);
target.sys_created_by = userID;
target.sys_updated_by = userID;

 

Hi ZB,

 

I'm trying to achieve this by Transform map.However, I don't find the sys_ux_my_list in the target table. Can you please explain,how you have achieved this

Hello,
I need to say that I didn't used transform map for this solution. Although, I know what is the issue here. If you lookup System Definition > Tables and look for sys_ux_my_list, you will find on it's record that it is in application scope: @Servicenow/now-record-list-menu-connected 
Only when you are in this scope you will be able to select the target table. 

ZB_0-1715174466771.png


Yet again being in this scope would probably require Source table to also be in this scope. Not sure how to approach it but maybe it will be possible to have staging table in the correct scope first. Maybe this would help: 
Staging table Target table not visible KB 

I ended up with AW lists exported to .xml and updated manually before insert 



 

 

Community Alums
Not applicable

Thank you. This helped us too!