power-pages

Power Pages Site Source

Purpose: emit Power Pages site source that pac pages upload accepts -- pages, templates, snippets, security -- backed by Dataverse, with Liquid templating and secure table access.

When to Use

• Generating an external/partner/customer portal over Dataverse from a PRD-LOWCODE
• Adding a page, web template, or secured list/form to an existing site
• Reviewing table permissions and web roles before go-live

Mental Model: The Site IS Data

Power Pages content lives in Dataverse tables (adx_* / mspp_*), not files. pac pages download materializes it to disk as YAML + content files; pac pages upload writes it back.

<site-root>/
  websites/<site>.website.yml
  web-pages/<page>/
    <page>.webpage.yml             # page metadata, parent, page template
    content-pages/<page>.<lang>.webpage.copy.html   # body HTML/Liquid
  web-templates/<name>.webtemplate.yml + .webtemplate.source.html
  content-snippets/<name>.contentsnippet.yml
  basic-forms/<name>.basicform.yml      # form over a table
  lists/<name>.list.yml                 # grid over a view
  table-permissions/<name>.tablepermission.yml
  web-roles/<name>.webrole.yml
  page-templates/<name>.pagetemplate.yml

Liquid Templating

Power Pages renders Liquid server-side before HTML. Use it to read Dataverse and site objects.

{% raw %}
<h1>{{ page.title }}</h1>
{% fetchxml issues %}
  <fetch top="10">
    <entity name="agx_issue">
      <attribute name="agx_name" />
      <filter><condition attribute="statecode" operator="eq" value="0" /></filter>
    </entity>
  </fetch>
{% endfetchxml %}
<ul>
  {% for row in issues.results.entities %}
    <li>{{ row.agx_name }}</li>
  {% endfor %}
</ul>
{% endraw %}

Key objects: page, user, website, request, settings, snippets, plus entityform / entitylist Liquid tags and the fetchxml tag. Liquid runs with the visitor's web roles -- it cannot bypass table permissions.

Security Is Mandatory (Default Deny)