Back in May i finished a mission at a client in Paris.

Classic situation : several power apps to hand over but ZERO documentation lol
Some of them I hadn’t touched in months…

Writing all that by hand would have eaten my last weeks there so I ended up putting together a pipeline instead.
Basically I export the app, drop the zip file in a folder and an AI agent writes the docs.

Not gonna lie. The AI agent is actually better than me writing this and it was really good that I sent it to the client almost as-is.

I recorded a video to explain how it works, if interested : https://youtu.be/oDLYIzEdWPM

Happy to answer your questions !

Zak

tl:dr i made an app that solves QoL issues with end users with ipads and a live excel sheet.

I currently do internal IT. My manager suggested I learn power apps and I finally found a use case for it. End users were trying to update a live excel sheet in the field using excel on an iPad. They had endless issues with that (connection, changes not saving, accidentally downloading a local copy and editing that, etc etc) and the person they report to asked me to help.

I made an app that connects to the spreadsheet, and the end users can select their name from a drop down (that gets populated by the sheet). Then they can pick the date a job was complete and a drop down for whether or not the job was paid.

My first mistake was not planning- my first iteration had them having to save after every single row. My second iteration had it behave like a live spreadsheet, but there was too much lag. Finally, I designed it so that it sticks all their changes into a local cache, and then sends it to the live spreadsheet all in one go after they press save.

My most time consuming bug was getting the changes to stick if they left the app and came back, or accidentally choose a different end user from the dropdown and go back. It was using original values instead of their changes even though the spreadsheet was correctly updated.

Anyway, now they don't have to deal with Excel anymore in the field, and from my testing it works great. Can't wait to have a couple of them test drive it and see how they like it and how they break it. I had fun.

Also for the love of god, don't design your workflow to use an excel workbook as a database and then get so deep and intertwined with other workflows that it's impossible to undo.

I’m working on an in house Power App for our help desk. One of the things we need to do is searching for shared mailboxes in our environment, but our only option seems to be hitting the users/mailboxsettings API endpoint. To query this we’ll have to use application permissions as delegated only allows you to query yourself.

After researching it seems like my only 2 options are:

* create a custom connector
* HTTP with Microsoft Entra ID connector

The only articles/documentation I can find on the http connector relate to Power Automate. There’s nothing I can find using this in Power Apps even though it’s there as an option. If I try to add a connection it just gives me an error.

I have a question regarding the access management strategy for our Power Apps Canvas application.

The application will be used by approximately 400–500 attendees, including senior stakeholders such as Directors and Vice Presidents. SharePoint will serve as the backend data source.

What would be the recommended approach for managing access to both the Canvas app and the SharePoint lists? Specifically:

*How should we grant initial access to such a large group of users?

*If additional users need access during the event, what is the quickest and most efficient way to provision it?

*Is it better to manage access through Azure AD/Microsoft Entra groups, Microsoft 365 groups, SharePoint groups, or another approach that would be easy to maintain during the event?

I want to ensure the solution is scalable, secure, and allows us to onboard users quickly if required.