Issues moving PA dashboards between instances

[Uncle Rob]

So I created a PA dashboard with two tabs & a dashboard breakdown.   Tab 1 has 9 report widgets and two Static HTML content blocks.

Tab 2 has 4 PA Widgets with a couple widget indicators each.   When I moved update set to test, I received these update set preview errors:

At first I thought I was on crack, and didn't have my update set "on" before configuring.   So I started all over.   Fresh update set.   New dashboard.   Same content.   Same update set errors when pushing to test.

I feel like I must be missing something obvious.

[Uncle Rob]

If the update set is committed, its clearly missing PAGE (sys_portal_page) records

[Andras Kisgyorg]

Hi Robert,

update_synch=false dictionary attribute exists on sys_portal_page table, which explains,

but still, this adds to the effort to move things across which are dependent on portal pages.

Best regards,

Andras

[Uncle Rob]

Why, why, WHY, WHY, WHY is that still a thing!??!

Fired.   Everyone is XXXXing fired!

[stefaan1]

Hi Robert,

It's still "a thing" because if the sys_portal and sys_portal_page tables were set to synchronize they would cause the default update set to be literally flooded with changes from the home pages (I was told admins were complaining). Whenever a user moves, adds or deletes a widget it causes the homepages to delete all related sys_portal records and recreate them all with new sys_ids.

This "system" is part of the reasons we want everyone to stop using homepages. On the other hand since Dashboards work differently than homepages used to, we can't just mass convert everything and force everyone off homepages.

There are books written about the difficulty of working with legacy code.