Microsoft PowerApps Review

Great UI and an easy initial setup, however, users are limited to 2,000 records

What is our primary use case?

We primarily use the solution as a general business process improvement. We use it as more of a digital transformation to eliminate some archaic manual processes that the business has built up over time. We're working to make everything more streamlined.

How has it helped my organization?

The solution has allowed us to remove a lot of manual redundancies and to update and streamline our processes.

What is most valuable?

It's easy to use due to expert UI. It is great.

The initial setup is easy.

There's a lot of online knowledge on the solution, to the point where new users can basically teach themselves how to use the solution.

What needs improvement?

The solution is limited in a very specific way. One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records.

I connect to an Oracle server that has well over 150,000 records that business users want to see or could use at any given time. The only thing that I could surface in the app is a portion of up to 2000 records at one data call.

Due to this limitation, I have to build in options for the user to refine the search, to go back out to the server, and then pull back records that match that search as opposed to offering all 150,000+ records. You need to filter quite extensively. Microsoft refers to is as a "delegation issue".

For how long have I used the solution?

I've only been using the solution for about a year. It hasn't been too long as of yet.

What do I think about the stability of the solution?

The stability has been very good. We've been pretty satisfied with it. It's not buggy. It doesn't crash.

What do I think about the scalability of the solution?

You cannot scale with PowerApps. PowerApps is still very much a point solution. The size is the size.

How are customer service and technical support?

We've dealt with technical support in the past. Everybody that we've worked with at Microsoft is phenomenal. They are always willing to help troubleshoot and get to the bottom of issues. That said, with PowerApps and even Power Automate, sometimes the teams at Microsoft still don't know why some issues occur or how to work around them.

Which solution did I use previously and why did I switch?

I joined the company a year ago in September. I don't think they used anything prior to that beyond the citizen developer level. There might have been a solution that the actual coders used, however, I can't recall the product's name. It was a pretty standard Microsoft application in any case. It may have been Visual Studio.

How was the initial setup?

The initial setup is not complex. It's quite straightforward.

For me, just using it on my own, I just used Google searches or YouTube to figure out how do this or fix and tie items together. After about a month of learning and experimenting, I had a pretty good handle on how PowerApps works.

What about the implementation team?

The company as a whole used Microsoft consultants to set up a center of excellence. 

What's my experience with pricing, setup cost, and licensing?

The solution is free if you have a Teams account, or Office 365. 

If you start to use any premium connectors that are not stored in a SharePoint list or on an Excel workbook, then it costs $4 per user per month. If you want unlimited, it's about $16 per month for unlimited apps and unlimited connectors.

There might potentially be a few other extra fees, however, I'm not sure what they are. Microsoft is one of those organizations that manage to nickel and dime its customers on everything.

What other advice do I have?

We're just a customer. We don't have a business relationship with Microsoft.

We are most likely using the most recent or updated version of the solution, however, I'm unsure of the exact version number.

While Microsoft is an option, I'd recommend users check out OutSystems first and see if it makes sense for them to use that before looking into Microsoft.

Overall, I'd rate the solution six out of ten.

Which deployment model are you using for this solution?

Public Cloud
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Microsoft PowerApps reviews from users
...who work at a Computer Software Company
...who compared it with OutSystems
Add a Comment