Load Page

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens

Reads the details of a DNN page into tokens: name, title, parent page, description, keywords, dates, URL, permissions and custom settings. You choose which details to load by giving each one a token name.

The page can be the current page, or one identified by its ID, path or name.

note

This action is part of the Portal Management add-on, which is installed and licensed separately (feature package PORTAL). If it isn't licensed, the action fails with a not-licensed error.

Typical Use Cases

• Prefill an edit form with a page's current name, title and description before Update Page
• Find the parent of a page, for example to build a breadcrumb or move a page
• Check which roles can view or edit a page
• Read custom page settings saved by Create Page or Update Page

Don't use it to

• Check whether a page exists and stop if it doesn't. If no page matches, the action does nothing and raises no error. Check the tokens afterward instead.
• Load a page from another portal. Paths and names are looked up in the portal the action runs in.
• Read the page's modules. Use Load Module instead.

Related Actions

Action Name	Description
Create Page	Creates a new page.
Update Page	Changes a page's details.
Export Page	Exports a page, including its modules, as XML.
Load Module	Reads a module's details into tokens.
Load Portal	Reads a portal's details into tokens.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Page Identifier	The page to load. Leave it empty to load the current page. Otherwise enter a page (tab) ID, a page path such as //Projects//Alpha, or a page name. It's tried in that order: a number is always treated as an ID, then a path is looked up, and then the first page with that name is used.	Yes	empty string	No

Output Parameters Reference

Each parameter is the name of a token that receives a value. Square brackets are optional. Leave a parameter empty to skip that value.

Parameter	Description
Store Page Name in	Receives the page name.
Store Page Title in	Receives the page title.
Store Parent Page ID in	Receives the parent page's ID, or -1 for a root page.
Store Parent Page Name in	Receives the parent page's name, or an empty value for a root page.
Store Page Description in	Receives the meta description.
Store Page Keywords in	Receives the meta keywords.
Store Start Date in	Receives the start date as a short date in the server's culture, for example 10/1/2026. It isn't set if the page has no start date.
Store End Date in	Receives the end date as a short date in the server's culture. It isn't set if the page has no end date.
Store Page URL in	Receives the full URL of the page.
Permissions	A list of permissions to load. In the first column, enter a permission key (for example VIEW or EDIT) or name (for example View Tab). In the second, enter the token name that receives the IDs of the roles that are granted that permission, separated by commas, for example 12,15. Denied permissions aren't included.
Other Settings	A list of custom page settings to load. In the Name column, enter the setting name. In the Value column, enter the token name that receives the setting's value. If the page doesn't have the setting, the token isn't set.

Considerations

• No match, no error. If the identifier doesn't match a page, the action ends quietly and no tokens are set. Use a condition on the next actions, for example [PageName] != "".
• Names are ambiguous. Only the first page with a matching name is used. Prefer IDs or paths.
• Page paths put // before each level, and spaces and other symbols are left out of the page names, for example //AboutUs//OurTeam for the page Our Team under About Us.
• Numbers are treated as IDs. A page named 2026 can't be found by its name. Use its path instead.
• Empty identifier needs a page. In a workflow or API with no current page, leave the identifier empty and the action fails with Could not get current page.
• Role IDs, not names. The permission tokens hold role IDs. Use them with actions that accept role IDs, or look up the names separately.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Load a page for editing

This action loads the page whose ID is in [SelectedPageId], and saves its name, title, description, parent ID, URL, view roles and a custom ProjectId setting in tokens.

{
    "Title": "Load Page",
    "ActionType": "LoadPage",
    "Description": "Load the selected page",
    "Condition": "[SelectedPageId] != \"\"",
    "Parameters": {
        "PageId": "[SelectedPageId]",
        "PageName": "PageName",
        "PageTitle": "PageTitle",
        "PageDesc": "PageDescription",
        "ParentPageId": "ParentPageId",
        "PageUrl": "PageUrl",
        "Permissions": [
            {
                "name": "VIEW",
                "value": "ViewRoleIds"
            }
        ],
        "OtherSettings": [
            {
                "name": "ProjectId",
                "value": "PageProjectId"
            }
        ]
    }
}

Revised 09/27/2026