Skip to content

Passing a value into an Aurena custom page through its declared 'initcontext' parameter (as documented for page development) via the URL doesn't work — appending the parameter as a normal query-string value (?ParamName=value) results in an empty/unset value inside the page.

Answer

For an initcontext parameter specifically, use a semicolon before initcontext rather than a question mark, following this pattern: .../web/page/PageClient/PageName;initcontext=ParamName:'value'. This is a different URL mechanism from OData-based page filtering (which does use a question mark for its own $filter query string) — initcontext is Aurena's own page-initialization-parameter mechanism and uses the semicolon convention instead, which is easy to mix up with the more commonly-referenced $filter syntax.

← Browse Platform, Aurena, and customization questions