Leave Request Template Not Working

[MattBowman]

Hi,

PowerApps newbie here. I've been investigating PowerApps as a cleaner alternative to just using Sharepoint / Power Automate / Forms to manage annual leave requests.

Using the Leave Request template, turning it into my own app and checking the data connections (O365 Users, O365 Outlook) are functioning, saving and attempting to run the app gives a very broken experience. 

All the navigation options to the left are missing, buttons to create new requests do not do anything and other screens are only accessible if the app is started on that particular screen.

The app checker shows 180+ errors:

I have tried saving and reloading the app, re-adding the data connections etc and nothing seems to be working.

Does anyone have any advice or solutions for this?

[TheRobRush]

we will need to see the errors to be able to help you resolve them.

[MattBowman]

Apologies, I thought I had uploaded an image containing details of some of the errors. Please see examples below. 

These errors all appear immediately after doing the 'make your own version of this app' step and selecting OneDrive for Business and the appropriate data connectors. So I'm sure I'm doing something very basic or fundamentally wrong here. 

[TheRobRush]

check whatever the Items property of the gallery - GalleryRequest & GalleryRequestDetails are. These sources either do not yet exist, or have not been properly  added to the data sources of the app yet

[MattBowman]

Thanks, I'll look into that but I am a bit confused as none of the step-by-step guides that reference this template seem to encounter any of these errors. 

I don't understand how 180+ things can break like that including all the in-app navigation. 

Is this expected behavior for this Template immediately after going through the 'make your own version of this app' step? Every other thread or tutorial for this I see doesn't mention going through and correcting all these errors.

[TheRobRush]

Try removing these two connectors and readding them. Upon doing some reading through past issues on these forums it seems they may sometimes not set up properly in the initial setup. /Can/ result in the issue you are describing

[cdrom1019]

I've been trying to make and modify this app for my department and I am having the EXACT same set of issues. I have literally begged people on support forms to do what you did just to see if they could re-create this and confirm I'm not insane. Thank you so much for documenting this. I feel a little better knowing that I can probably remedy a lot of this by re-adding the data connectors, but I'm having my own set of internal company problems with those that we're working to correct.

Have you made any progress correcting the formulaic errors since this thread?

[cdrom1019]

Update 1. So I managed to brute force my way through a bunch of errors. I've got more but this is progress. I noticed when I was working on this template that I was missing a data sources button. Turns out, power apps depreciated some features a while back, so now I'm curious if the template was dependent on these being enabled. 
But I enabled Improved Data Source Experience and Relational Data in advanced settings. Then I removed the sharepoint lists I was working with and relinked the data excel spreadsheet that came with the template via one drive. That knocked out over 100 formulaic errors. Going to see if I can brute force the rest of these. 
Keep me up to speed with anything you find out please.

Update 2: Hey! I think I figured it all out. I managed to clear all the formula errors and got the thing working like I needed it to. I'm flat amazed.   So take my advice and open 2 versions of this app, the power apps template and in another window, open the version you're modifying. This way you can compare your apples to apples and find changes in the code that don't make sense. After the nonsense with the data sources were figured out, I eventually realized a lot of the formula errors were caused by some small changes in the code. A lot of the datasets it was trying to pull from were suddenly showing as ICON.value instead of just value. Like ICON.Leave or ICON.balance.

If you remove ICON. from each of these, and use the app checker to point you to each one, the errors should clear up. Refresh the page when you've got all the formula errors cleared and the navigation options should show back up.

[MattBowman]

Outstanding effort! I'm going to give this a go as soon as I get the time to work on this again! 
(also relieved to know that it wasn't just me doing something very fundamentally wrong and that the code for the template is in fact borked).

[kyonettech]

Thank you for your hard work with this! This resolved the issue for me. I also struggled to find documentation regarding this template so I was happy to come across this post. I'm curious to find out if you developed any further with this, perhaps including hours/half days as an option for requesters?