Power Pages Solution Architecture Patterns: When to Use Liquid vs. JavaScript vs. Power Automate
In Power Pages, you can implement logic in multiple layers — Liquid (server-side), JavaScript (client-side), or Power Automate (external workf...
In Power Pages, you can implement logic in multiple layers — Liquid (server-side), JavaScript (client-side), or Power Automate (external workf...
Why Client-Side Caching? Power Pages often fetch data from Dataverse using Liquid, Web API, or Power Automate. But repeated calls can slow dow...
When building Power Pages (formerly Power Apps Portals), performance is just as important as functionality. Users expect fast-loading pages, e...
Use Power Fx in Power Pages (Preview) Power Pages is getting smarter! Until now, most of the logic you could add to forms and pages had to be ...
What are Cloud Flows in Power Pages? Cloud flows allow you to: You configure this using the Power Pages + Power Automate integration via the “...
In today’s low-code/no-code world, Copilot in the Power Platform ecosystem is a game-changer — especially for Power Pages developers. It bring...
Liquid is a powerful templating engine, but it needs to be used thoughtfully — especially in enterprise-grade Power Pages projects. Below are ...
What is Liquid in Power Pages? Liquid is an open-source server-side templating language originally developed by Shopify — and it’s a core part...
In Dynamics 365 Field Service, a work order refers to a task or a job needing to be scheduled or assigned to someone. They generally include i...
In the world of Field Service, maintaining Service Level Agreements (SLAs) is critical for customer satisfaction and compliance. But technicia...