We have a page include we are updating with the children of a master report. The problem is when we attempt to update the page include with a different child-of-the-master page, the page include will render the master page elements with the intended child-of-the-master page metadata, but will attempt to render the first component of the page region of the originally loaded child-of-the-master page.
It’s a very odd behavior - it appears that the child page is not loading correctly on update page include when the child page is what is being included.
Debug_PageIncludeChild_SampleUpdateInclude
<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" useviewportmeta="true" showheader="true">
<models/>
<components>
<buttonset uniqueid="sk-3qMSjX-449" position="left">
<buttons>
<button type="multi" label="Show Child A" uniqueid="sk-3qMrF9-522">
<actions>
<action type="custom" snippet="ShowChildA">
<onerroractions/>
</action>
</actions>
</button>
<button type="multi" label="Show Child B" uniqueid="sk-3qMrHm-527">
<actions>
<action type="custom" snippet="ShowChildB"/>
</actions>
</button>
</buttons>
</buttonset>
<includepanel type="skuid" uniqueid="sk-3qDBDT-210" pagename="Debug_PageIncludeChild_DefaultBlank" module=""/>
</components>
<resources>
<labels/>
<javascript>
<jsitem location="inlinesnippet" name="ShowChildA" cachelocation="false">$ = skuid.$;
var pageInclude = skuid.$('#'+'sk-3qDBDT-210').data('object');
pageInclude.pagename = 'Debug_PageIncludeChild_ChildA';
pageInclude.load();</jsitem>
<jsitem location="inlinesnippet" name="ShowChildB" cachelocation="false">$ = skuid.$;
var pageInclude = skuid.$('#'+'sk-3qDBDT-210').data('object');
pageInclude.pagename = 'Debug_PageIncludeChild_ChildB';
pageInclude.load();</jsitem>
</javascript>
<css/>
<actionsequences>
<actionsequence id="43f58ef3-9233-424b-9311-14b4f8196862" label="New Sequence" type="reusable">
<description/>
<actions>
<action type="save"/>
</actions>
</actionsequence>
</actionsequences>
</resources>
<styles>
<styleitem type="background" bgtype="none"/>
</styles>
</skuidpage>
Debug_PageIncludeChild_Master
<skuidpage unsavedchangeswarning="yes" personalizationmode="server" useviewportmeta="true" showsidebar="true" showheader="true">
<models/>
<components>
<richtext multiple="false" uniqueid="sk-3qCkZb-637">
<contents>&lt;p&gt;Rich Text component on master page.&lt;/p&gt;
</contents>
</richtext>
<pageregion uniqueid="sk-3qCiKE-627">
<styles>
<styleitem type="background" bgtype="none"/>
</styles>
</pageregion>
</components>
<resources>
<labels/>
<javascript/>
<css/>
<actionsequences/>
</resources>
<styles>
<styleitem type="background" bgtype="none"/>
</styles>
</skuidpage>
Debug_PageIncludeChild_ChildA
<skuidpage unsavedchangeswarning="yes">
<models/>
<pageregioncontents>
<pageregioncontent regionid="sk-3qCiKE-627" uniqueid="sk-3qCxvi-205">
<components>
<richtext multiple="false" uniqueid="sk-3qCzqC-225">
<contents>&lt;p&gt;Rich Text component on child A. A1&lt;/p&gt;
</contents>
</richtext>
<richtext multiple="false" uniqueid="sk-3qC_F_-236">
<contents>&lt;p&gt;Rich Text component on child A. A2&lt;/p&gt;
</contents>
</richtext>
</components>
</pageregioncontent>
</pageregioncontents>
<components/>
<resources>
<labels/>
<css/>
<javascript/>
<actionsequences/>
</resources>
</skuidpage>
Debug_PageIncludeChild_ChildB
<skuidpage unsavedchangeswarning="yes">
<models/>
<pageregioncontents>
<pageregioncontent regionid="sk-3qCiKE-627" uniqueid="sk-3qCpf6-205">
<components>
<richtext multiple="false" uniqueid="sk-3qCrdk-225">
<contents>&lt;p&gt;Rich Text component on child B. B1&lt;/p&gt;
</contents>
</richtext>
<richtext multiple="false" uniqueid="sk-3qCr-L-236">
<contents>&lt;p&gt;Rich Text component on child B. B2&lt;/p&gt;
</contents>
</richtext>
</components>
</pageregioncontent>
</pageregioncontents>
<components/>
<resources>
<labels/>
<css/>
<javascript/>
<actionsequences/>
</resources>
</skuidpage>
Debug_PageIncludeChild_DefaultBlank
<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" useviewportmeta="true" showheader="true">
<models/>
<components>
<richtext multiple="false" uniqueid="sk-3qQWSQ-210">
<contents>&lt;p&gt;DefaultBlank&lt;/p&gt;
</contents>
</richtext>
</components>
<resources>
<labels/>
<javascript/>
<css/>
<actionsequences/>
</resources>
<styles>
<styleitem type="background" bgtype="none"/>
</styles>
</skuidpage>
Here are the five page definitions needed to demonstrate the issue.
Debug_PageIncludeChild_SampleUpdateInclude is the page you’ll look at for demonstration.
Before I go make 5 pages, which org are you in? Are you in 10.x or 11.x?
It looks like all of this is done with code instead of using declarative Skuid. Is there a reason why this is? Why not use the page include component Skuid offers declaratively?
The code was shorter - we were observing the same behavior with the declarative method. I’ll see about putting together the declarative pages when I have the time and will submit a new thread if I observe this behavior in a more recent version of the platform.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.