When should I use power page?

(0) Share

Report

Posted on by Ray

Hi,

Recently I came across this blog.

I am a developer in the Power Platform and Dynamics CRM area. I have some questions about Power Page.

1. When should I use Powe Page for my application? As a developer, I think learning the Liquid language is a high-cost thing and not like JS or C#, it can only use in Power Page as I know. I used to build external sites with MVC.

2. What are the benefits and disadvantages?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

Squire4Hire 125 on at

Like (1)

Report
Copy link

Link copied!

In my opinion, wait another year or two for Microsoft to catch up. Power Pages is grossly under-developed and I'm surprised they actually green-lit it for public use at the current state it's in.

It lacks proper documentation, and what documentation is out there is muddled up with Power Portals. The templates are mucked with bad code that is poorly represented (most likely they've been sloppily pulled in from Power Portals which isn't a 1-to-1 comparison). The UI is janky in anything more complex than the very basics of HTML and CSS. You have to leap through hoops to make the minimal expectation to work. And, unless you have a heap of experience in Power Portals, it is extremely unintuitive.

There are many platforms out there that do use Liquid syntax - especially in the e-commerce realm - so it's not a complete loss to learn, but if you do take the Power Pages route, prepare for a lot of frustration, and expect your project to either take much longer than you expect, or be far less polished than you would hope.

Was this reply helpful? Yes No
Verified answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

@RayGan wrote:
Hi,

Recently I came across this blog.
I am a developer in the Power Platform and Dynamics CRM area. I have some questions about Power Page.
1. When should I use Powe Page for my application? As a developer, I think learning the Liquid language is a high-cost thing and not like JS or C#, it can only use in Power Page as I know. I used to build external sites with MVC.
2. What are the benefits and disadvantages?
So if you've been in the CRM space for a while you may be familiar with Adx Studio or Dynamics 365 Portal or PowerApps Portals (basically all the same thing re-branded). Power Pages is the next incarnation with a view to simplify (low code) the creation of sites - but the backend is currently the same.

1. You need a Portal for external (or internal) users to access your CRM/dataverse data.
(you can build your own portal from scratch e.g. MVC and host it yourself or use Power Pages)
Liquid is not propriety to the Portal/PowerPages but there are some propriety elements - it originates from Shopify (https://shopify.github.io/liquid/). Depending on what you need to do you can put something together without writing any Liquid yourself.

2. Get something secure up and usable quickly. Main disadvantage is that you do not have full control of the layer between the Page and Dataverse and so there are limitations that you would not have with a completely custom built portal.

Was this reply helpful? Yes No