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

Nikita35
Kilo Guru

I added some reports to my dashboard, "Unload the dashboard" in the Update set and moved it to test.

I get 30 errors - "Could not find a record in sys_portal for column portal_widget referenced in this update" for the reports which are added I believe. I already ignored the errors and committed the update set.

Now my dashboard layout is all messed up.

when I created another update set to capture missing updates of sys_portal, I see they are not capturing in the update set.

Do I need to import and export the xml? 

how can i resolve this? 

4 REPLIES 4

Milind Gharte
Kilo Guru

Hi,

 This page below explains how to add a home page, which is a sys_portal_page, to an update set.

GlideappHome.unloader(current);

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

 

If it helps,Please mark Correct and 👍 Helpful.

Warm Regards,

Milind

thanks Milind for reply

I have created another update set to capture the fixes.

And I have unload the portal page as in above document.

But this has only captured the portal page - "sys_portal_page" not missing "sys_portal" records.

This gives only one record in my update set.

 

I am not clear Where do I need to write this command ? 

GlideappHome.unloader(current);

Or only Unloading the page is going to solve the issue?

or Do I need to import and export the xml the missing sys_portal records?

When you click on unload portal page and move that update , then all sys_portal_page and sys_portal, both errors get resolved.

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.