Recently I was asked about executing a FetchXML query using the Web API in Power Pages, and while you won’t find any specific documentation on that in the Power Pages documentation, you’ll be happy to know that it is supported. In this blog post, I’ll look at how its done.
Independent Software Vendors (ISVs) have been an important part of the Microsoft Business Applications space for a long time. ISVs create solutions that build on top of the platforms and products that Microsoft provides off-the-shelf. As the Power Platform has continued to grow and evolve, more opportunities have presented themselves for ISVs. In this post, I’ll look at what ISVs might want to consider when looking at incorporating Power Pages as part of their offering.
Microsoft’s Power Platform is constantly growing and evolving. As much as everyone (especially Microsoft) wishes that all parts of the Power Platform worked seamlessly together, the reality is that many parts of the Power Platform existed long before Microsoft started using the word Power to group these technologies together. However, I believe that advancements in virtual tables, specifically for Power Pages, emphasizes the fact that Dataverse should be at the core of any Power Platform implementation.
The price point for Power Pages has long been a tricky discussion point. The pricing model has changed a few times of the years, and organizations can feel frustrated if they are on the wrong end of who ends up paying less and more when the model changes. In this blog post, I’ll review the history of the pricing for the product, and provide my opinion on whether I think the cost is justified by the value.
The growth of Power Pages has been an amazing story. Since being acquired by Microsoft in 2015, the product has gone from a niche add-on for Dynamics 365 Customer Engagement to a full-fledged product in the Power Platform. The visibility that comes with getting equal billing to other Power Platform products like Power BI, Power Apps, and Power Automate means that new people are discovering Power Pages all of the time. However, as with any software product, Power Pages isn’t always a fit, even if your project fall under the category of low code web application development platforms. In this post, I will share what I look for when trying to determine if Power Pages is a fit for a given project.
For the most part I don’t blog about the (roughly) monthly releases for Power Apps Portals, mostly because they deal with bug fixes for relatively obscure issues. However, last month I was happy to see a few items on the list that I’ve been waiting for, and I thought were worth sharing.
A question popped up a couple weeks ago about the best way to force everyone to have to login to your Power Apps Portals before getting access to anything. At first I gave a very wrong answer – thankfully MVP Nick Doelman corrected me, and in the process, we all learned another thing about licensing.
In the summer when I did a series of posts on one way of customizing the registration process for Portal users, Dileep Singh (@rulesrchanged) – the head of Power Apps Portals at Microsoft – reminded everyone not to forget about how you can customize the registration experience if you’re using Azure AD B2C. In this post, I’ll go through the steps to do just that.
Azure AD B2C is Microsoft’s preferred identity provider for Power Apps Portals. In this post, I’ll provide an overview of the technology, why it’s Microsoft’s preferred identity provider, and a few tips on how to set it up.
Last time I gave an overview of authentication with Power Apps Portals, and I mentioned that external authentication is the way to go. In this post I dive a bit deeper into external authentication.
