ENGINEERED CODE BLOG

Power Apps Portals: Using Bootstrap Input Groups with Your Basic or Advanced Forms

The fact that Power Apps Portals uses Bootstrap as its CSS framework means we have a lot of tools as our disposal (yes, I know we’d all love it if we could use a newer version of Bootstrap, or even pick whatever framework we wanted, but that is a topic for another day). Unfortunately, some of the Bootstrap components require specific markup that we can’t achieve with configuration alone. In this post I’ll cover how we can use JavaScript to change the markup on either Basic Forms or Advanced Forms so that we can leverage the Input Group functionality (in case you missed the memo, Basic Forms is the new name for Entity Forms, and Advanced Forms is the new name for Web Forms).

Continue reading “Power Apps Portals: Using Bootstrap Input Groups with Your Basic or Advanced Forms”

Power Apps Portals: Adding Custom Styles to Legacy Front-Side Editor

While Microsoft continues to invest heavily in the Portals Studio, which provides a new What You See Is What You Get (WYSIWYG) editing experience for Power Apps Portals, there are still many good reasons to use the Legacy Front-side Editor. In this post I’ll describe how you can add additional styling options to the rich text editors to allow content authors to create consistent pages.

Continue reading “Power Apps Portals: Adding Custom Styles to Legacy Front-Side Editor”

Power Apps Portals: Related Entity as Source of Next Web Form Step

The Web Forms functionality lets you build complex multi-page, multi-entity wizard-style forms on your Power Apps Portals. And while there are a ton of options, it’s not uncommon to run into situations where you can’t do everything you want with configuration, so you might need to resort to a bit of JavaScript (and maybe even Liquid). One of those situations is if you want the source entity for the next step in your Web Form to be a record related to the entity of the current step.

Continue reading “Power Apps Portals: Related Entity as Source of Next Web Form Step”

Power Apps Portals: Related Records Filtering on Lookups When Creating Records via Subgrid

The power of Entity Forms in Power Apps Portals is that they mirror much of the functionality available in model-driven apps (and Dynamics 365). While the parity isn’t 100%, one advanced feature that Entity Forms does support is Related Records Filtering on lookups, where the available options in the lookup are filtered by some other data that has already been selected. However, in certain cases, this functionality doesn’t offer exact parity out-of-the-box – one of those cases is when you are creating a new record via a subgrid, and you’re expecting that the parent record is used in the filtering of the lookup.

Continue reading “Power Apps Portals: Related Records Filtering on Lookups When Creating Records via Subgrid”

Power Apps Portals: Customizing the Rendering of Notes and Activities

I’ve always been an advocate for using CSS to control the visibility of out-of-the-box Power Apps Portals features. Unfortunately, sometimes CSS isn’t enough, and you do have use JavaScript. And even then, sometimes you have to resort to some exotic techniques – one of those times is customizing some aspects of how notes and activities are rendered on Power Apps Portals.

Continue reading “Power Apps Portals: Customizing the Rendering of Notes and Activities”

Power Apps Portals: Rich Text Editor on Entity Forms

I’ve been asked a few times about how you can add a rich text editor to Entity Forms or Web Forms on Power Apps Portals, and while I haven’t had the need to do this for a real implementation, I was curious to try it out. In the process, I found out about a setting I didn’t know existed that’s been around for at least a few years.

Continue reading “Power Apps Portals: Rich Text Editor on Entity Forms”

Power Apps Portals: Modifying Option Set Options on an Entity Form

If you’ve come from the world of Dynamics 365 (or CRM…) and are starting to work with Portals, it can be frustrating when you discover that client-side JavaScript code that works great in your model-driven app doesn’t work on a Power Apps Portal – especially because Entity Forms and Web Forms are marketed as a technology that exposes your existing forms to the web. This post we look at why it doesn’t translate, and provide some code that solves a common request: modifying the available options in an option set.

Continue reading “Power Apps Portals: Modifying Option Set Options on an Entity Form”

Power Apps Portals: Where You Put Your JavaScript Matters

One of the most frustrating things that can happen when developing any type of software is when you’ve got the code correct but, due to it being in the wrong place, it doesn’t work as you’ve expected. A recent question on the community forums highlights the importance of putting your JavaScript in the right place.

Continue reading “Power Apps Portals: Where You Put Your JavaScript Matters”

PowerApps Portals: Liquid and JavaScript – Better Together!

PowerApps Portals offers two primary languages for customization: JavaScript and Liquid. This leads to confusion as to which technology should be used when – I’ll try to clear up some of that confusion in this blog post, as well as demonstrate that is many cases, the best option is a combination of the two.

Continue reading “PowerApps Portals: Liquid and JavaScript – Better Together!”

Contact

Engineered Code is a web application development firm and Microsoft Partner specializing in web portals backed by Dynamics 365 & Power Platform. Led by a professional engineer, our team of technology experts are based in Regina, Saskatchewan, Canada.