Skip to content

Engineered Code Blog

Category: Liquid

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

March 12, 2020 3 Min.To Read

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.

Power Apps Portals: Print Invoices

March 5, 2020 3 Min.To Read

The topic of my first Portals Community Call back in January was the how to build a portal that allows a customer to view and print invoices. While solutions for this has been described by others (including Megan V. Walker’s excellent post), I also presented a different approach that I thought was worth covering in a blog post so that I could get a bit more into the technical details.

Power Apps Portals: fetchxml Liquid Tag and Entity Permissions

January 16, 2020 3 Min.To Read

The fetchxml Liquid tag is arguably the most powerful Liquid tag in Power Apps Portals – it allows you to meet complex requirements for the display of data. But, if you combine it with a complex Entity Permissions model, you could find yourself getting unexpected errors. In this post I’ll cover what can cause those errors, and how to work around them.

PowerApps Portals: Liquid and JavaScript – Better Together!

October 31, 2019 4 Min.To Read

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.

Back to top