Thinking about it, there might be a way of doing this already using the event stuff… Hmm…

There is a way to do what you’re looking for with the parameters attribute, which accepts a JSON string of parameters to pass in to the underlying Skuid page. Each key in the JSON object will become a Page Parameter available within the Skuid Page.

<aura:component implements="flexipage:availableForAllPageTypes" access="global" >

    <skuid:page page="OrderList" parameters='{"foo":"bar"}'/>

</aura:component>

Unfortunately, there’s not much you can do with these parameters within Skuid at present. We’re working to resolve this for the Millau Update 1 release, which is coming out in mid-February.

Hey Zach, did this ever make its way into the release? I’m trying to think of the easiest way of passing the record id to a Skuid page embedded in a lightning component (in a Community). I can pass the id by publishing an event but was wondering if I could just pass it as a parameter as above, and if so, how would I reference that parameter in the page?

Cheers!

Louis

Oh wow! I think this is working fine? Human error yesterday. Nice! So this is a great way to pass the recordId into a Skuid page from within a Lightning Component!

Cheers!

Here’s how it works, for anyone who’s interested. Create a component like this (implementing whatever else you need to get it to work where you want it to):

<aura:component implements="force:hasRecordId">

    <aura:attribute name="skuidParams" type="String" />

    <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>

    

    <skuid:page page="YOUR_SKUID_PAGE" parameters="{!v.skuidParams}"/>

</aura:component>

And add this to your lightning controller:

({

    doInit: function (cmp, event, helper) {

        

        // Get the record Id

        var recordId = cmp.get('v.recordId');

        

        // Set params in an object

        var params = {

            "id": recordId

        }

        

        // Convert object to JSON

        params = JSON.stringify(params);

        

        // Set those params in an attribute on the component

cmp.set("v.skuidParams", params);

    }

})

Louis, thank you for continuing to update this thread as you’ve worked on this. It’s definitely relevant as more customers are working towards moving to Lightning. I’m glad Zach was able to offer a good response in January, and I’m going to bring this to our documentation team as a topic that warrants further exploration.