For the second time in a few years, Power Pages is making the news for all the wrong reasons. In mid-November 2024, Aaron Costello of security firm AppOmni published an article describing what he called “a significant data exposure issue within Microsoft Power Pages”. Let’s look at what he discovered.
A question I recently saw on the Power Platform Community forums asked why would someone use Power Apps (I’m assuming they are referring to canvas apps) instead of Power Pages. They mentioned that using Dataverse with Power Apps requires a premium license, so I think the implication is that Power Pages might be a cheaper option. In this blog post, I’m going to look at some of considerations when making the choice between Power Pages and Power Apps (both model-driven and canvas).
When building a website with Power Pages, there are a few different interfaces that are available. If you’re new to the product, it can be a bit confusing to know what they all are, and what they are used for, especially because there can overlap between them. In this blog post, I’ll do my best to help reduce some of that confusion.
Recently there was a comment on Power Pages Tip #222 – List Calendar Styles on our YouTube channel – they were asking about adding a click event handler to events being displayed on a list that is using the calendar functionality. In this post, I’ll show you one way of doing that.
Over the last few years, we’ve been working on ecLearn – a Learning Management System (LMS) built on top of the Microsoft Power Platform. It allows organizations to create and deliver courses using either a model-driven Power App or Power Pages. As I’ve described in previous posts previous posts, delivering an ISV product using Power Pages is not without its challenges. In this post, I’m going to look at one particular issue we ran into during our development.
A few months back, I wrote an article about how to handle the change event for multiselect (choices) columns on Power Pages forms. Another common requirement is handling an event when the page first loads – this can be useful in situations where you want to modify the available options based on other values on the page. In this post, I’ll look at how you might be able to do that.
Most months this blog covers technical topics related to Power Pages. However, this month marks a special milestone for us here at Engineered Code – on May 27th, we’ll be celebrating 10 years in business. So I though I’d take a break from the technical stuff and instead take the opportunity to reminisce a little bit.
With the release of documentation describing the migration from the Standard Data Model to the Enhanced Data Model, we’ve entered some unprecedented times for organizations that have been using Power Pages for a long time. For the first time since Microsoft acquired the product, a significant upgrade of the website will be necessary at some point in the future to transition to both Bootstrap v5 and the Enhanced Data Model.
This month we continue our look at some of the pro code techniques that appear in the templates available for Power Pages. We’re going to stick with the “Schedule and Manage Meetings” template, which provides a multistep form for booking a meeting. This time we’re going to look at the second step, where a user can select which location they want their appointment at. This step includes some custom JavaScript, plus a PCF Control.
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.
