There are certain cases where you can do everything you’d think is required to setup an editable Entity Form, yet for some reason it keeps appearing as read-only. In this post, I’ll explain why. Spoiler alert: I don’t have a great workaround for this problem, but to save some other people the headache of trying to figure out what’s going on, I thought I’d put together a quick post.
A couple of weeks ago I shared a solution for supporting multiselect option sets on a PowerApps Portal (they aren’t currently supported out-of-the-box), however it only worked for creating new records. If you want it to work for updating existing records, there is a bit more work to do, but thankfully not that much!
There are some areas of PowerApps Portals that are still implemented using either ASP.NET MVC or ASPX, instead of via Web Templates, which means the configurability options are limited – one of those is the Knowledge Base (which exposes Knowledge Article entities). Often we can use Liquid and JavaScript to customize some of these areas, but there is one thing in particular that makes doing this for the Knowledge Base challenging – in this post I’ll explain what that is, and how to get around it.
