Navigating from one custom page to another with parameters

[Harry1]

Hi all, I hope someone can help.

I am trying to go from one custom page to another while passing through parameters, I have tried using the launch function passing in the URL of the custom page within the model driven app however that simply returns an error whilst simply only passing in the URL works fine but does not allow me to include any parameters to carry into the other custom page: 

Found here: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-param

I have also tried using the Navigate function as highlighted in the custom page docs but these docs give no information about how to carry over parameters to use in the other page so it does not seem to be useful in this case:

Found here: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/page-powerfx-in-model-app

So if anyone can point me to another way to navigate to other custom pages from custom pages which allow me to include parameters I can use in the second custom page or can tell me any parameters I have missed, I would be very thankful.  Is this the kind of thing which would require custom JavaScript or is this something that can be doe innately in the system?

[Brendan1]

Ok, so I ended up going a different route.  I used navigate() and was able to pass in a record:

Navigate(
    First(Users),
    {Page: 'Custom Page Display Name'}
)

On the other custom page, I used the following in OnStart:

Set(
    varRecord,
    LookUp(
        Users,
        User = GUID(Param("id"))
    )
);

I was then able to use it in my page. Example:

varRecord.'Full Name'

so far, I haven't found a way to pass in any other parameters.  I tried creating a custom record to pass in parameters, but that didn't work:

Navigate(
    {Param1:"foo",Param2:,"bar"},
    {Page: 'Custom Page Display Name'}
)

It's a bit hacky, but if I need this functionality (might do with my current project), i'll probably write a dataverse record and use that for parameters:

UpdateContext({
    MyRecord:Patch(
        MyTable,
        Defaults(MyTable),
        {
            Column1:"foo",
            Column2:"bar"
        }
    )
});

Navigate(
    Lookup(MyTable,myrecordid=MyRecord.myrecordid),
    {Page: 'Custom Page Display Name'}
)

I'd probably write a flow to cleanup the table every 24 hours as well.

@davidyc , I did try your URL parameters, and they work as expected.  Thanks for coming back to that.

There is the same limitation here though too, you can't pass your own custom parameters along the querystring.

Cheers,

Brendan

[sagarnagadiya]

This works perfectly for me. Navigating from one custom page to another custom page. Also, I tried navigating from power page to MDA entity record page. Both scenario works fine using Navigate(). 

[Sawh]

Hi Brendan,

I will try your Navigate() approach and see if that’ll work for me. Thanks,

ange

[Sawh]

That didn't work for me. All I get are error messages on both pages.

Ange

[dpatterson_dl]

I recently stumbled upon the same limitation. Unfortunately, you are very limited on the parameters that can be passed to a custom page. For custom-pages, the only parameters accepted by the page are: recordId and entityName. You can see that limitation called out in a "note" under the "Param" section of Microsoft's documentation - https://learn.microsoft.com/en-us/power-platform/power-fx/reference/function-param#param

The ability to pass some other kind of application state as a parameter for custom pages is not possible. 

[Da_Dude]

This is an old thread, but I just stumbled on it.

I have worked around not being able to pass in multiple parameters by instead passing in an array of parameters converted to a string in the "recordId" parameter. Then, onStart of my app, I use Split() to convert back to array and pull my parameters out in the order I put them in to initiate different variables in my app. 

This obviously introduces potential ALM concerns, but it works and if you are the one writing the JS and the Custome Page, then it should be fairly easy to manage.