Hi, @Torro27.
I'm on a roll today and it seems that your post may be nearly buried. (it was on Page 3 when I found it). I haven't used Access Web Apps before but I've been developing in PA for the past few months. Here are my thoughts about PowerApps (PA).
- Setting up forms in PA can be a hassle if you have some relationships between entities (e.g. Parent-Child, Many-to-Many, etc.) There's a bit of a learning curve in creating forms too.
- PA is advertised as no-code but to do some complex stuff (it doesn't even have to that complex), you would eventually have to do some code. PA code is a lot similar to that of Excel but there are some subtle rules that you have to be aware of.
- One huge disadvantage of PA involves delegation.
Reference: https://docs.microsoft.com/en-us/powerapps/delegation-overview
tl;dr Some data-retrieving functions (e.g. aggregate functions like sum) can only work with the first 500 records it sees. If you have a large enough dataset, this might be a problem. - CDS, as far as I've read in the forums (I haven't had experience with it), can be disastrous at times. There have been reports of data loss, unannounced down times, data corruption, etc. Use it at your own peril. (Or it may have improved over the past few weeks, I don't know)
- Here's one piece of good news. You can do tablet layouts in PA. (I did all of my organization's apps in tablet layout). Some templates do not have this option but you can start a table layout from scratch.
I'm tagging some of the support staff here to get their attention. @v-micsh-msft, @v-monli-msft -- Help this guy out? Please and thank you.
Wish you the best of luck, dude. PA hasn't been really fun for me but then again, I was here on its early stages. (Well, earlier). Hope you do better. 😄
