How does everyone organize their power platform solutions? I’m setting up a developers guide with naming conventions but can’t decide which would be best for simplicity but organized.
My gov contracting company wants to build a power apps for preventative maintenance. I’m not the most knowledgeable in databases so help me out here.
This seems like a pretty big back end. It started off with a simple ticketing application and it has turned into wanting a PMS application that support the tickets.
I’m familiar with using SharePoint lists and understand it can go pretty far with views and filters. But I still don’t feel comfortable using it as a backend for an application that would be used for 400+ people.
I suggested another database like SQL…?? I tried dataverse but I think they saw the price of it and decided it wasn’t worth it. Maybe I need support to back up dataverse…. IDK.
All users will have a power apps license. Options if they didn’t have a license ??
I need all the help I can get
I initially created an application that was only supposed to used by a small team, however it has reached a point where they are wanting over 200 B2B external accounts to use this application. It’s essentially a ticketing application using SharePoint lists. They also want to make it so just about anyone could submit tickets, which is basically impossible because they would need a license to interact with the app..?
They’re willing to pay for licensing just to use the app but I feel like essentially for the same price, I could built a web application on our Azure Gov Cloud. Removing all the licensing limitations and having a better database.
Anyone done anything like this? Any advice?