Natvigation Master Page - Trying to convert a prior page into a child page
Hi,
I had previously built some pages in Skuid. I have upgraded to the latest Banzai release. I have decided to build a navigation menu. I followed the Skuid tutorial to create a Navigation header. It is saved as a Master Page. I now need to:
1) Discover the best way to incorporate the navigation menu throughout my app. I did not want all of my app pages to display in Skuid. I simply want to use the navigation to open SFDC pages.
Q: Is this possible? If so; can someone help me learn how to accomplish?
2) Secondly, until I can discover how to accomplish Question #1, I tried following the tutorial to take an existing page and use its XML in a Navigation Master Page child page. I was hoping I could do this to take my existing Skuid pages and use them with the navigation. This would be a workaround to what I am trying to accomplish as outlined in Question #1. However, after following the instructions in the Master Page tutorial article regarding merging the XML into a child page (since there is no other way to accomplish); when I select Preview noting shows but the Master Page Navigation. The page region content doesn't show.
Q: Can someone look at my child page XML to make sure it is set up properly. There was only one mode in the Navigation Master Page which was User based off of the tutorial.
If so; I can send you the XML for the child page.
I had previously built some pages in Skuid. I have upgraded to the latest Banzai release. I have decided to build a navigation menu. I followed the Skuid tutorial to create a Navigation header. It is saved as a Master Page. I now need to:
1) Discover the best way to incorporate the navigation menu throughout my app. I did not want all of my app pages to display in Skuid. I simply want to use the navigation to open SFDC pages.
Q: Is this possible? If so; can someone help me learn how to accomplish?
2) Secondly, until I can discover how to accomplish Question #1, I tried following the tutorial to take an existing page and use its XML in a Navigation Master Page child page. I was hoping I could do this to take my existing Skuid pages and use them with the navigation. This would be a workaround to what I am trying to accomplish as outlined in Question #1. However, after following the instructions in the Master Page tutorial article regarding merging the XML into a child page (since there is no other way to accomplish); when I select Preview noting shows but the Master Page Navigation. The page region content doesn't show.
Q: Can someone look at my child page XML to make sure it is set up properly. There was only one mode in the Navigation Master Page which was User based off of the tutorial.
If so; I can send you the XML for the child page.
Tagged:
1
Categories
- 7.9K Questions
- 926 Ideas
- 220 Discussion Categories
- 178 General
- 9 Community Feedback
- 3 Community Info
- 18 Knowledge Base
Comments
Not sure exactly what you mean by question 1... you just want your Skuid header to open SFDC pages that are not squidified, but retain your skuid header? Not sure if that's possible. Why not just squidify your whole app and get rid of the SFDC layouts entirely?
If you just want your skuid header to be links to SFDC pages with a normal SFDC header, that's totally possible.
If you post your XML we'll take a look.
I followed the Master Page Tutorial instructions below:
Can I send you my child page XML? I'd like to know what I am doing wrong.
----see tutorial description below-------
First, copy the models you want into the <models> section and rename any models that have the same name as any models on your Master Page. Then, in the <pageregioncontent><components> section, paste in the components from your existing page and remap them to your new model names as necessary. (I learned that one the hard way too).
There will be a <pageregioncontent> node for each of the Page Region components in the Master Page, so you can either paste all the component XML into one, Save, and then drag/drop components around in the App Composer, or go ahead and arrange them in the XML.
Send both your original page and your new child page.
Your components need to be inside the pageregioncontents tag, like so:
Are the components visible in the builder?
Are you getting any console errors in runtime?
I am not getting any errors in runtime.
Were you ever able to get this to work?
If you have a working stand-alone page that you want to convert to a child page:
I just followed the instructions again. Its not working for me. I did this several times the other day and provided my XML.
Here is a tutorial on how to give us login rights: http://help.skuidify.com/m/getting-started/l/182412-getting-help-how-to-grant-skuid-login-rights-to-....
I was trying Matt's syntax above, with no avail. Then I discovered that I was missing a 'regionid' and a 'uniqueid' as attributes of the <pageregioncontent> like this:
<pageregioncontent regionid="sk-1Ko4TE-313" uniqueid="sk-1K_4ce-72"><br>
To obtain it, I went into the page editor, dropped any random component into the new child's pageregion, returned to the XML editor, and voila - the id's are now populated.
Just remove the XML of the component you randomly selected, and follow the 'Special Considerations' here.
FYI, there's now a child-normal page converter tool in Skuid Labs.https://github.com/skuid/skuid-labs/tree/master/experiments/pages/childNormalPageConverter