Answered

Unexpected Error with Query Parameter in Power Pages Portal

(1) Share

Report

Posted on by CU26111754-0

I'm encountering an issue in my Power Pages portal when using year as a query parameter in the URL. Here’s the scenario:

When the URL is structured as ?activationId=<value>&year=<value>, I receive the error:
"The year query parameter is not supported."
However, if I swap the order to ?year=<value>&activationId=<value>, it works fine.

The year parameter's value is correct (a valid record ID), and the error only occurs when year is used in the second position of the query string.

I've ensured proper URL encoding for all parameters..

How can I use year as a query parameter without causing this issue?

Categories:

Customize & extend

All responses (5)

Answers (1)

Sort by

Suggested answer

SaiRT14 1,992 Super User 2025 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Some query parameter names (like year) may conflict with reserved words or built-in functions in the Power Pages framework, causing unpredictable behavior. or The order of query parameters may affect how they are parsed if specific logic is implemented in the portal or custom scripts.

The simplest fix is to avoid using year as a query parameter. Instead, use an alternative name like yearId, yr, or customYear. - ?activationId=<value>&yearId=<value>

let me know whether it fixes your issue?
CU26111754-0 30 on at

Like
a
(0)

Report
Copy link

Link copied!

i rename year with other param also but it also not working,

The error i got on console
{"code":"9004010B","message":"The [param_name] query parameter is not supported"}
Verified answer

CU26111754-0 30 on at

Like
a
(0)

Report
Copy link

Link copied!

The error is solved but instead of passing as query param can we use js cookies or session storage.How we can retrieve them using liquid code. I didn't found anything for that
Suggested answer

Fubar 17 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Liquid can't read local storage etc as it runs server side - you would have to implement that in JavaScript on the receiving page.

My question would be, how were you adding the url paramter that you were having the issue with? (and is it a field value on the current record?)
Suggested answer

oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

I just tested this and didn't have any issues, do you have any custom Liquid code that could be validating on all request params that could be throwing this error?