Describe the bug
I have a site that leverages cloud flows on the standard data model to perform certain server-side actions and returns that data to the site. But trying to download the site using the pac CLI requires using the excludeEntities.
I have another site that it works fine on and uses the new data model.
GitHub Copilot has this to say:
The PAC CLI uses different code paths for each model:
Enhanced (v2): Downloads via powerpagecomponent table which stores relationships as JSON within the component - no N:N intersect table needed
Standard (v1): Uses the actual adx_cloudflowconsumer entity with a separate adx_CloudFlowConsumer_adx_webrole N:N intersect table
The bug is in PAC CLI's Standard model handler - it tries to query adx_CloudFlowConsumer_adx_webrole by logical name but fails to find it in its metadata cache, even though the table exists (we proved this by querying it directly with FetchXML).
Root cause: Cloud Flow Consumer was likely added to Power Pages after Microsoft stopped actively updating the Standard model code path in PAC CLI. The N:N relationship metadata lookup is broken for Standard model sites.
Desktop (please complete the following information):
- OS: Windows
- Browser: Edge
- IDE: VS Code
Additional context
pac pages download --overwrite --path "PATH" --webSiteId SITEID --modelVersion "1" --excludeEntities "adx_cloudflowconsumer"
Describe the bug
I have a site that leverages cloud flows on the standard data model to perform certain server-side actions and returns that data to the site. But trying to download the site using the pac CLI requires using the excludeEntities.
I have another site that it works fine on and uses the new data model.
GitHub Copilot has this to say:
The PAC CLI uses different code paths for each model:
Enhanced (v2): Downloads via powerpagecomponent table which stores relationships as JSON within the component - no N:N intersect table needed
Standard (v1): Uses the actual adx_cloudflowconsumer entity with a separate adx_CloudFlowConsumer_adx_webrole N:N intersect table
The bug is in PAC CLI's Standard model handler - it tries to query adx_CloudFlowConsumer_adx_webrole by logical name but fails to find it in its metadata cache, even though the table exists (we proved this by querying it directly with FetchXML).
Root cause: Cloud Flow Consumer was likely added to Power Pages after Microsoft stopped actively updating the Standard model code path in PAC CLI. The N:N relationship metadata lookup is broken for Standard model sites.
Desktop (please complete the following information):
Additional context
pac pages download --overwrite --path "PATH" --webSiteId SITEID --modelVersion "1" --excludeEntities "adx_cloudflowconsumer"