Can you use URL Parameters with Microsoft Power Pages?

[JameHealy]

Is it (or will it be) possible to use URL Parameters with Microsoft Power Pages?

I don't mean query parameters (or 'querystring' parameters), but rather URL parameters. For example:

• Query Parameter:domain.com/path?key=value
• URL Parameter: domain.com/path/value

For example, if I have an entity/table like "Staff", I could use use something like: domain.com/team/johnsmith to point directly to a page template that is filled with the johnsmith record in the Staff entity/table.

Ultimately, it allows me to use page templates and manage content in my datasource (e.g. Dataverse), without editing the page itself. It also helps with SEO.

(All other major Content Management Systems, like Wordpress, Drupal, and even newer ones like Webflow are able to do this).

[Conax]

I don't think you can, if you are using Entity Forms, as they work on record id passed to the URL.

But if you build your own display form, you can use the liquid template request object (https://learn.microsoft.com/en-us/power-apps/maker/portals/liquid/liquid-objects#request) to get the parameter values and then construct fetchXML to get the data to display on the page.

[OliverRodrigues]

Hi, not sure if this would help, but take a look at this article: http://oliverrodrigues365.com/2021/03/02/power-apps-portals-loading-large-data-in-entity-lists/

might be a starting point

[Anonymous]

Yes, for example;

If your URL is like https://abc.powerappsportals.com/xyz-page?yourparametername=parameter-value 
You can reference it in your code as {{request.params.yourparametername}} to retrieve its value.

You can also use it in your liquid code as something like 

{% if request.params.yourparametername == value %}

<p> something here </p>

{% endif %}

You can read more here: Custom URL Query Parameters for your Power Apps Portals – Franco Musso

[sweb]

@Anonymous

He wants to use url params, not query params.

request.params.yourparametername returns parameter-value the URL is ?yourparametername=parameter-value

But if the url is /something/else?yourparametername=parameter-value

He wants /something/else, maybe one of them or both.

What I could find is request.path, it would return /something/else, and you'd have to work your way to get each param since it just gets the URL path.

[Fubar]

@sweb I agree they are asking about using the path. 

I wouldn't recommend doing it, but something is probably possible.  The portal/power pages does not natively support dynamics paths.  if the url path does not match a defined Web Page short name hierarchy you will get page not found. Which means the only place you could attempt to apply your logic is behind the "Page Not Found" Web Page or its Web Template.

As you can get the path as a string you can then probably use the the Liquid string filters (e.g. 'split' filter) to separate out the parts in the path.