Here’s the link if you missed the previous post

We’re building an absence tracking system with SharePoint and PowerApps. Last time we set up two lists in SharePoint, one which will hold the actual absence requests and the other holding the remaining absence allocation for each employee.

Today, I’ll be adding the lists to teams and I’ll customise the form of the requests list.

Adding the form to SharePoint

This part can be done quickly – just go to Teams, open the HR Public channel, we created, click on the little plus icon on the top, select the list we created and we’re done.

But this doesn’t give us the best user experience:

Users don’t know what this list is about and they can’t infer just by the list title. They need more context, they need more instructions.

In SharePoint, that’s very easy to do. Let’s create a SharePoint page and wrap the list inside it.

We can add a nice header image and friendly text in the beginning, like this

Perfect! We’re done with adding the list to Teams.

Customising the form

Let’s look at how the list appears at the moment:

There are way too many fields to enter here. In most cases, it’s enough to just remove the fields from the default SharePoint form, but we have a more complicated case here. You can read my other blog post, where I compare the built-in forms with customised ones

Customising the form

To customise the form, we can use the “Customise with PowerApps“:

This opens up the PowerApps interface. We can remove all the extra fields now and only keep the start and end date:

This is the final form:

I’ve also added more labels to the fields, so it’s easier for the user to understand. I’ve also remapped the “Approved” field to “Yes/No” instead of true/false:

I’ve applied conditional showing and hiding of the “Approved” card:

Wrapping up

That’s it for this part. There are two steps/parts left:

• Implementing the flow
• Cancellation logic

Let me know if I missed anything important.