upgrade to lightning with minimal fuss

  • 1
  • Question
  • Updated 2 months ago
  • Answered
I want to upgrade to lightning experience with minimal fuss to our large user base that have only recently moved off the classic interface, into a fully customised Skuid interface.

The sole reason for switching to lightning would be to grant our users access to the vastly improved reporting UI.

We're using classic, though the users wouldn't know this as our tab bar at the top of the page is a Skuid master page with object tabs.

Currently when a user clicks the "Reports" tab, they're taken back into the classic interface where they can view and create classic reports, it's not the most elegant solution, and could definitely be improved, though it does the job.

I have a couple of ideas.

1.  I'd like to explore (if at all possible) is keeping the top bar which would include a link to the lightning reporting interface....has anyone done this before? This would be the smoothest transition for us.

or

2.  Change our Skuid page theme to a lightning theme and utilize the lightning search bar capabilities among other cool things lightning now offers. 

I've quite quickly been able to add an existing Skuid page to a lightning page. Though you'll see from the screenshot below I have my master page included too, which isn't desired seeing as we have the lightning top bar too.

So my question, how do I remove the master page from a Skuid page without having to manually recreate the whole page? Is there anything in the XML I can do to achieve this quickly?

Photo of Glenn Daly

Glenn Daly

  • 1,686 Points 1k badge 2x thumb
  • confused

Posted 2 months ago

  • 1
Photo of Matt Davis

Matt Davis, Employee

  • 1,562 Points 1k badge 2x thumb
If you want to recreate a Skuid page without the Master page, you can do that with some XML. What I would do is create a new page and add one of each resource (model, component, action sequence, js, and/or css if applicable), then save the new page. This just makes the xml a bit easier to read in my opinion, since it'll have a node for each of these.

Now copy & paste in the similar node from the Original to the NewPage one node at a time. So copy & paste over everything between <models> and </models>. Then similar for components, action sequences, js, and css. Components is the only one I think is a bit of extra work, since it'll be nested under the <pageregioncontents> node in the Original.