All posts tagged PowerApps

The other day I was tinkering around with a request to have different fields hidden based on the mode (New, Edit, View) the SharePoint form was in. The process seemed to be pretty straight forward, but for some reason it didn’t quite work out as expected. I finally figured out the cause and thought sharing the steps for creating dedicated PowerApps forms for each mode in a SharePoint list might help others out.

How Not To Do It

So first off let’s start with how not to do it. The settings are located as properties of the SharePoint Integration object in your solution.

Properties of the SharePoint Integration Object

I had thought that by simply calling the EditForm function and passing the form I had used for editing, it would automatically load for me:

PowerShell

1

EditForm(SMRequestForm_Edit)

Unfortunately this did nothing.

Creating Dedicated PowerApps Forms for Each Mode in a SharePoint List

So above we are telling the form that we want to declare our edit form as the SMRequestForm_Edit, but we aren’t actually telling PowerApps how to get there. So we just need to add a little bit of code that tells it to move to that particular screen:

As you see in the screenshot below, I have actually done something similar for all of the forms. However, I haven’t created a View Form yet so it is looking at the EditForm.
Check out the transition in action:

Preparing for Updates

One thing I would like to suggest you do is add a bit of code at the beginning of the transition component that tells your form what stage you are at. This is to assist with any custom code you might want to add depending on the form stage you are at (I will be covering this in a future post). Simply modify your code by adding the initializing and setting of a variable (I called it formStage).

This is the final post in my series of building a modern SharePoint Solution. In this post, I will demonstrate starting a Microsoft Flow from a PowerApp. There are many reason’s why you would want this, but the most often used would likely be to allow the user to update an entry, save it and hold off sending it until they have all the information in place. There are alternatives of course; like having a Flow wait for a value to change, but I prefer the user experience a button submission gives you. Special note: Because Flow doesn’t currently allow for multiple triggers for a flow, we won’t be able to use flow created in Part 9 of this series. However, I do suggest you not remove not remove it because this allows multiple ways to kick off the WF.

Welcome to the next part in my series about building a modern solution in SharePoint. This post we are going to cover integrating PowerApps as a custom list form in your solution. When PowerApps was first released, Microsoft made sure that everyone knew it wasn’t built for SharePoint. In fact the first examples that Microsoft provided didn’t even involve SharePoint. Since then SharePoint lists and libraries can be accessed by PowerApp forms using connectors into those environments. Finally, in the final quarter of 2017 Microsoft provided the ability to integrate PowerApps directly into a list form, thus overriding the default forms of a list. So like the InfoPath forms of days gone by, you can now use PowerApps for creating, editing and viewing data in your lists. This post will cover setting up a PowerApp for these list forms. The next post we will customize the form more to meet our needs for this solution.

Continuing my series on building a modern SharePoint solution using PowerApps and Flow I want to show how to go about setting a SharePoint people picker field programmatically in PowerApps. This goes back to one of the requirements listed for my solution in part 1 of this series: “Requestor’s manager should be auto-populated as an approver”. What’s nice about this is the manager field is filled in already by the company’s administration system. It exists in Azure AD and thus within Office 365, which just so happens to have a connector that easily allows us to build with it. I am getting ahead of myself though. Let’s dig in and learn how to do this.

In this third post in my series on modern SharePoint solutions, I will cover customizing PowerApp forms to meet the requirements of the business. We’ll first start off with some basic customizations that need to be done for most form integrations. When I started to write this post I initially had planned to discuss the modifications you should make for all and then move on to the custom modifications for the solution requirements. The “default mods” quickly filled up this post, so I have moved the custom mods to the next one.