Portex Install

XrmToolBox plugin

Power Pages development, in one workspace.

Edit portal files, see how security connects, run queries as a contact, and open the live site. Dataverse stays the source of truth. Portex uses the connection you already have in XrmToolBox.

Install in XrmToolBox GitHub

01 — Code editor

Portal files, in an editor that saves back to Dataverse.

  • Web templates
  • Content snippets
  • Web files
  • Web pages

Browse a website’s files and edit them in Monaco. Save writes to Dataverse. Bind Azure DevOps when you also want a lock and a commit, with a personal access token and no app registration. Standard and enhanced Power Pages data models both open here.

Portex code editor showing the Web API Helper web template beside the file tree for the Mock Insurance site.
Web templates open beside the portal file tree.

02 — Security analysis

A map of who can reach which tables.

Pick a web role and Portex draws its table permissions, parent relationships, and the tables they grant. Filter by contact, web role, or table and the map rebuilds around that slice. Access trace walks one contact through the same model.

Security map for the Policyholder web role, linking table permissions to mock policy, claim, payment, and contact tables.
Policyholder, expanded from its web role to the tables those permissions grant.

03 — Query executor

Run the query the way the portal would.

Execute FetchXML as a portal contact, so that contact’s web roles and table permissions apply. Rows come back under the query, with the raw payload and the server, plugin, and portal traces in the next tabs. Web API calls and Liquid renders use the same contact.

FetchXML query against mock policies, executed as the User-Admin portal contact, with three result rows.
FetchXML for policies, executed as User-Admin.

04 — Live portal viewer

The real site, already signed in.

Choose a website and a portal profile. Portex opens that site in the contact’s session, including a private site, and can clear the portal cache from the toolbar. Traces turns the same page load into the Dataverse and Liquid work behind it.

Live Mock Insurance portal signed in as User Admin, with the home page open inside Portex.
The live site, opened as a portal profile.
Portal traces for a page load, listing Dataverse RetrieveMultiple calls with duration and cache state.
Server trace for that page load: Dataverse operations, Liquid, and the slow calls.

Install it where you already work.

Free to download and use, including at work. Open the Tool Library in XrmToolBox and install Portex. It takes the Dataverse connection that is already open.

Get Portex GitHub