Everyone knows that PowerApps Forms are much trickier than their siblings - PowerApps Apps. So when it comes to creating a multi form experience it's not the same for PowerApps Forms. In fact Microsoft PowerApps Team recommends using a Patch function or other workarounds. So officially multi forms for PowerApps Forms are not supported. It's obvious why one would like to use multiple forms over a huge single form - a better user experience and a natural feel. So it is doable and the benefits of using it the way I described below are: No extra buttons. While a custom button can compliment your form and expand its functionality, you still have standard buttons you cannot hide. All columns can stay required on a SharePoint level. The forms will react to those required fields as needed. No Patch function. Don't get me wrong, the Patch function is very useful but…

Even out of the box PowerApps is a great tool that provides lots of functionality. Way more than InfoPath could. However, most of the time with very few adjustments it is possible to achieve even more. A great example would be a Combo Box and its search ability. Let's create a SharePoint list with a Choice column and these values: It doesn't really have to be a Choice column, you might as well use a Lookup column. When a PowerApps form is created, the studio creates a Data Card and a Combo Box control associated with that Choice field. Let's see how the search in that Combo Box works and why it is limited in its current state. Note how it finds BK but doesn't find Black. The search has a StartsWith behavior. What if it is necessary to search for a word regardless of its position. Well, that's very easy…

As far as I know at the time of this post PowerApps doesn't have an Input Mask (currency mask in this particular case) feature. It is possible to mimic that feature using Text function but implementing it is not really straightforward and gets even more complicated if you are dealing with PowerApps integrated with SharePoint. In this post I will show you 3 different ways of implementing a workaround for a currency input mask, each has its own pros and cons: The currency mask formatting is not visible until you submit the form (the simplest). You can see the mask formatting even before submitting your form but you need to click away from the field to see the formatting (medium complexity). The currency formatting is applied real time as you type in the numbers (the most complicated but the most natural way of working with currency). Let's create a testprice…

I am huge advocate of using as few columns as possible when building PowerApps forms in SharePoint. Let's take a look at a very simplified example - a custom Requests SharePoint list.  It surely has to have fields like: Requested By (a user name here) Requested On (a date and time here). So rather than creating two more columns and populating them with values, I would highly recommend using columns that already exist in SharePoint - Created and Created By. The downside of these columns is they don't have values until a user submits the request. Because of this it might be not the cleanest user experience if you decide to use and show those fields. There is a simple way to prepopulate those fields with values that will be exact (user name) or very close (date and time) to the ones that will appear after submission. Let's create a…