When looking at the create a ticket system, have you considered the connection to Office 365 users and groups in stead of creating new users in the app? With this you do not need to manage users on the app. Only thing is when a users leaves the company, there will not be any user connected to a ticket. But when users leaves, the ticket is no longer interesting for us

I’ve done a lot of research over the last 9-10 months on solutions to queries I have in Power Apps. Some of which were probably too advanced for my skills at the time. Nevertheless, I followed guidance on YouTube and eventually modified what I saw to work to my needs. I probably didn’t understand why it was working but I made it work. I then came across @Darren Neese and the Learn Power Apps community. There is so much useful information and guidance offered that I recently purchased the PPC course to advance my knowledge. That brings me back to why I’m posting. One thing I would like to see on the channel is a solution to dynamically drag and drop for tasks. i.e. having a list of tasks/jobs that I can drag and assign to a user/time slot just like scheduling our production or maintenance jobs. I found a really good solution by Scott Durow where he provided a component which allowed me do it (link below). https://youtube.com/playlist?list=PLhgOm-Jpmt82JvLdJFx3Zqo89h_deWJQF&si=Iioh8BXLOVnosTqz It was fairly in depth and took me a lot of time to get up and running, but I did get it working, well sort of. I could drag and drop my tasks but could not figure out how to get the Patch back to my datasource to work as I was trying to adapt his instruction to my app needs. Like I mentioned earlier, I was probably trying to achieve something far too advanced for my understanding at the time. If I looked at it again, I may stand a better chance of achieving the final goal of saving my drag and drop changes. Is it possible to come up with a solution that achieves a similar result without the need for installing the components that Scott provides? It’s a big ask but, if I’ve learned anything, you have to think a bit out of the box and that’s what this community and its contributors do best.

Hi all, is there any coding and design standard guide or check list available for Power Apps digital workflows? Pls can someone help me. Thanks

Am still figuring this out but am trying to see the differences in setting up model driven apps over a canvas app. Wondering the advantages and limitations and if a template can be used. Have decided on the template need for sure but want to understand the template's use if the app is model driven or if that is still pending for the toolkit.

How can C# (and Visual Studio (Code)) can be used for Power Apps Development?