Could not find a record in sys_portal for column portal_widget referenced in this update

haitech
Mega Contributor

When moving update set to another instance, I get this error: 

Could not find a record in sys_portal for column portal_widget referenced in this update

Could not find a record in sys_portal_page for column page referenced in this update

Could not find a record in sys_portal for column portal_widget referenced in this update

 

I am trying to move dashboards to another instance from another but these errors occurs every time. Could this be because they are somehow fixed in one instance?

7 REPLIES 7

codycotulla
Tera Guru

Hi,

I found this post because I was having the same problem. The sys_portal_page for a dashboard didn't get included in the update set.

It looks like this is intentional. This page below explains how to add a home page, which is a sys_portal_page, to an update set.

It explains that you need to unload the home page to get it into the update set. The command for unloading a portal page is where current is the GlideRecord for the home page.

GlideappHome.unloader(current);

This command pushes all the home page and its drop zones and stuff like that to the update set.

Hope this helps someone.

Thanks,

Cody

Timothy F1
Tera Guru

If someone is looking for the instructions for fixing this with a dashboard, this KB from ServiceNow is helpful: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0761169

In the workaround it walks through the process for Unloading a dashboard, which is what you have to do to properly move a dashboard between instances.

SonakshiK
Tera Contributor

Hi,

This error is due to the records in sys_portal and sys_portal_page for the dashboard is not found in the target instance.

The solution I found while facing this was to export the xml of these records(your dashboard specific records from sys_portal and sys_portal_page) and import them to the target instance first. After importing the xml, if you migrate the update set, you should no longer face this error and the dashboard layout or reports should not be messed up or empty.

Thankyou.