power-pages-liquid

Power Pages Liquid

Microsoft Power Pages (formerly Power Apps Portals) uses a DotLiquid-based Liquid dialect that talks to Dataverse. It shares the base Liquid grammar with Shopify but has a completely different tag/object/filter vocabulary. The most common failure mode is reaching for Shopify syntax that does not exist here.

Hard rules (these do NOT exist in Power Pages Liquid)

Don't write	Write instead
{% paginate products by 10 %}	{% entitylist name:"name" %} (built-in paging) or paginate manually with request.params['page'] + slice
{% section 'header' %}	{% include 'snippet_name' %} or {% include 'web_template_name' %}
{% schema %}	(delete) — themes are configured in the Power Pages portal, not in Liquid
{% layout 'theme' %}	{% extends 'page_template_name' %} (DotLiquid template inheritance)
{% form 'contact' %}	{% entityform name:'Form Name' %} or {% webform name:'Web Form Name' %}
{% style %} / {% javascript %}	raw <style> / <script> blocks
{% render 'x' %}	{% include 'x' %} (Power Pages does not support render)
product.title, products[...]	Dataverse: {% fetchxml %} or {% entityview %}; rows via entities['cr_product'][id].cr_name
collection.*, collections[...]	No collections. Query Dataverse tables.
cart.*	No cart. Custom or Dataverse-backed.
customer.*	user.* (current portal user / Dataverse contact)
shop.*	website.*, settings.*
linklists.main_menu	weblinks['Web Link Set Name']
block.settings, section.settings	No Shopify blocks. Use snippet params and web template attributes.
| asset_url, | asset_img_url, | img_url, | img_tag	Site-relative paths or | url. Write <img> tags explicitly.
| money, | money_with_currency, | weight_with_unit	Format manually via | string and arithmetic.
| stylesheet_tag, | script_tag	Raw <link rel="stylesheet"> / <script src=""> tags.
| handleize, | within	No handles or collection contexts.

A PreToolUse hook in this plugin hard-blocks Write/Edit/MultiEdit on .liquid files containing any of these. If a write is blocked, the stderr message names the offender and the fix — apply it and retry.

Core tag vocabulary

• {% entitylist name:"List Name" %}...{% endentitylist %} — render a configured Dataverse entity list (cards, table, filters, paging).
• {% entityview name:"View Name" entity:"logicalname" %} — render a Dataverse view by name.
• {% entityform name:"Form Name" %} — render a single-step entity form.
• {% webform name:"Web Form Name" %} — render a multi-step web form.
• {% include 'snippet_name' %} — include a content snippet or another web template.
• {% block name %}...{% endblock %} and {% extends 'page_template' %} — DotLiquid inheritance.
• {% chart id:"chart-id" viewid:"view-id" %} — embed a Dataverse chart.
• {% powerbi authentication_type:"..." path:"..." %} — embed a Power BI report.
• {% editable entity field:"name" %} — inline-editable content for portal authors.
• {% fetchxml q %}<fetch>...</fetch>{% endfetchxml %} — run a FetchXML query against Dataverse; results in q.results.
• {% searchindex query:"..." %}...{% endsearchindex %} — Lucene-backed portal search.
• {% assign %}, {% capture %}, {% if %}, {% for %}, {% case %}, {% comment %}, {% raw %}, {% cycle %} — standard Liquid control flow (supported).

See references/tags.md for full signatures and worked examples.

Core objects

• entities['logicalname'][id] — a Dataverse row by GUID.
• user — current authenticated portal user (a contact). Properties include id, fullname, firstname, lastname, emailaddress1, and any custom attributes; helper methods like user.has_role['Administrators'].
• page — the current web page (a Dataverse adx_webpage). page.title, page.url, page.parent, page.children.
• website — the current website (adx_website).
• request — request info: request.url, request.path, request.path_and_query, request.params['key'].
• params — alias for request.params.
• settings — site settings configured in the portal.
• snippets['Name'] — content snippets (HTML content authored in the portal).
• sitemap, sitemarkers['Marker Name'] — site navigation and named page anchors.
• weblinks['Web Link Set Name'] — configured navigation link sets.
• forloop, tablerowloop — standard loop helpers.

See references/objects.md.

Filters worth knowing

• liquid — render a string as Liquid (rare, powerful).
• url, url_escape — site-aware URL helpers.
• xml_escape, escape, h — output escaping.
• has_role — boolean check used like {% if user | has_role:'Administrators' %}.
• boolean, integer, decimal, string — type coercion (DotLiquid-specific).
• Standard: default, date, truncate, truncatewords, replace, remove, append, prepend, split, join, size, first, last, sort, reverse, where, map, upcase, downcase, capitalize, strip, escape, newline_to_br.

See references/filters.md.

Deep references

Pull these when the user's task needs more than the quick reference above.

• references/tags.md — every Power Pages tag with full signature and a worked example.
• references/objects.md — every object with available properties and sample access.
• references/filters.md — full filter list with DotLiquid notes.
• references/fetchxml-cookbook.md — common FetchXML query patterns inside {% fetchxml %} blocks.
• references/shopify-vs-power-pages.md — the anti-pattern crib sheet (mirrors the hook's enforcement list).
• references/recipes.md — end-to-end recipes (role-gated content, paginated entity lists, web form embed, chart embed, multi-language snippets).

Quick sanity checklist before writing a .liquid file

1. Am I about to use a tag from the Hard rules table? Stop, swap it.
2. Am I referencing product, collection, cart, customer, shop, or linklists? Stop, this is Shopify.
3. For a list of data: use {% entitylist %} or {% fetchxml %} — never invent objects.
4. For inheritance: {% extends %} + {% block %}, not {% layout %}.
5. For includes: {% include %}, not {% render %} or {% section %}.