We’ve been setting up an invoice processing system using the tool's document automation reference model. I’ve also been customizing the document automation reference app to create workflows for our organization.
Librarian at a media company with 51-200 employees
Helps to handle the reviewing and filing processes of invoices
Pros and Cons
- "Microsoft Power Apps has helped us handle our fairly complex invoices, including filing and reviewing them manually. We’re working towards automating our invoice processing, labeling them according to organization accounts, and developing an entirely digital workflow. The tool uses customizable AI models for your organization's documents, so it supports AI-driven projects well."
- "The solution's deployment is complex."
What is our primary use case?
What is most valuable?
Microsoft Power Apps has helped us handle our fairly complex invoices, including filing and reviewing them manually. We’re working towards automating our invoice processing, labeling them according to organization accounts, and developing an entirely digital workflow. The tool uses customizable AI models for your organization's documents, so it supports AI-driven projects well.
What needs improvement?
The solution's deployment is complex.
For how long have I used the solution?
I have been using the product for a couple of months.
Buyer's Guide
Microsoft Power Apps
December 2024
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
I rate the solution's stability a nine out of ten.
What do I think about the scalability of the solution?
Microsoft Power Apps is scalable. My company has two users for it.
How are customer service and support?
We get limited support if no payments are made for additional support.
How would you rate customer service and support?
Neutral
How was the initial setup?
I rate the tool's deployment ease a six out of ten.
What's my experience with pricing, setup cost, and licensing?
My company has non-profit licensing, and hence, it is affordable. Pricing depends on usage.
What other advice do I have?
I rate the overall solution a nine out of ten and would recommend it to others.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 30, 2024
Flag as inappropriateSr. Digital Experience Consultant at a computer software company with 5,001-10,000 employees
Provides a lot of flexibility for flow automation, very stable, easy to deploy, and good price
Pros and Cons
- "The model that allows you to establish flow automation is getting a lot of traction from the customer side. It offers a lot of flexibility."
- "The availability of templates needs to be improved. I understand that the ecosystem around it is still developing, but we need more templates. I would like the entire ecosystem around it to improve. I would recommend adding AI components. Even though we can always connect to Azure for AI components, they should slowly start looking at adding some AI components to PowerApps so that out-of-the-box learning can be applied to process flows. Salesforce has the Einstein layer that works along with license platforms. PowerApps should also have something similar."
What is our primary use case?
My organization deals with the implementation of PowerApps and Salesforce. We are currently scaling up our capacity in low-code, no-code platforms. Essentially, this solution is for building forms from a front-end loan application and quickly rate a particular application.
What is most valuable?
The model that allows you to establish flow automation is getting a lot of traction from the customer side. It offers a lot of flexibility.
What needs improvement?
The availability of templates needs to be improved. I understand that the ecosystem around it is still developing, but we need more templates. I would like the entire ecosystem around it to improve.
I would recommend adding AI components. Even though we can always connect to Azure for AI components, they should slowly start looking at adding some AI components to PowerApps so that out-of-the-box learning can be applied to process flows. Salesforce has the Einstein layer that works along with license platforms. PowerApps should also have something similar.
For how long have I used the solution?
We have been using PowerApps for the last six months in our organization.
What do I think about the stability of the solution?
I haven't come across any issues. I have not faced any issues with my existing deployment.
How was the initial setup?
It is quite straightforward.
What about the implementation team?
We have our own team for the maintenance side.
What's my experience with pricing, setup cost, and licensing?
One of the main things about this solution is the price. The cost for Salesforce is $35, $25, or $10 per user per month. PowerApps costs much less than that. It is at a good price point. It may change in the future, but at this point, its price is pretty fine.
What other advice do I have?
I would recommend this solution for people who are looking for flexibility. PowerApps offers more flexibility than SalesForce. I would advise others to use a local platform to build and test first and fail fast.
We are still exploring a few features, but based on what I have learned and seen, I would rate PowerApps an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Microsoft Power Apps
December 2024
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
Associate Director at a insurance company with 10,001+ employees
User-friendly, easy for beginners, and reliable
Pros and Cons
- "The solution becomes easier the set up once you get used to it."
- "It's easy to use."
What is our primary use case?
We predominantly use the product for a lot of intake forms. There is a lot of data collection and a lot of intake forms. We use Power Application for validation rather than using spreadsheets. It's good for automation, where we need a data repository of the input, which we get from the resource.
What is most valuable?
It's extremely user-friendly. It's easy to use. Of course, it's a local tool, however, if you're aware of some of the basic Microsoft products, you can really get on with it. That's something which is really wonderful.
Even a beginner can set up a Power App and run with it. That's one of the most important features when it comes to the adoption of Power Apps.
The solution becomes easier the set up once you get used to it.
It's a stable product.
The solution has the potential to scale.
What needs improvement?
I would like to see some of the connectors which they have right now to be more basic. The ones they have right now, they claim, are premium connectors. They should make that a little more affordable and have it in the free version. Some of the basic databases like SQL should be part of their normal connectors, and it should necessarily be premium.
It can be a bit more difficult to set up the first time.
They have a feature that integrates well with Power BI, however, it is not seamless. We'd like a better, more seamless integration with Power BI in the future.
They need more of a font selection. If I'm in Excel and I'm using a particular font, I'm limited in terms of which I can use. It should allow for use of any fonts under Microsoft 365.
For how long have I used the solution?
We've been using Power Apps for the last two years or so.
What do I think about the stability of the solution?
The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
It is scalable if we integrate with other applications like Power Automate and connect it with some other applications or some other databases like SQL. That said, in the current arrangement with SharePoint, we have some limitations. The moment the data increases, if we're able to integrate Power Automate, then surely it becomes a scalable application. Right now it can be scaled, however, it's not something that we are looking to do.
There are maybe 60 to 70 users at this point of time actively giving us data, however, there could be other applications that people are using.
How are customer service and support?
In terms of technical support, we do have a governance team. The IT governance is a security team who helps us navigate through issues. We raise requests internally within our organization to help us see where the issue is, and they will escalate as required. They might reach out to Microsoft support to kind of get it sorted. That said, we have not found any major issues so far. If we do, our internal team is the first team to go to.
Which solution did I use previously and why did I switch?
We previously used mostly manual consolidation using Excel, emails, and things like that. There was no other tool before. That said, we used normal Office productivity tools like Excel and Outlook. We went with Power App since we were already using Microsoft and Office 365, which helps us to integrate multiple other Microsoft solutions. That's the reason we thought Power Apps would be the best way for us. It also integrates with SharePoint and is easy to build in.
How was the initial setup?
The initial setup was not straightforward, however, once you get a hang of it, then it's pretty simple to create things. From a documentation perspective, it's kind of a good guide that they have as far as Power Apps is concerned. It's easy to get started. Like any tool, you have to spend some time understanding and navigating around it. There is just a normal learning curve that is required as with application. You won't really find it that difficult if you are ready to invest the time to learn the tool. There's a moderate level of complexity.
It was not that effort-intensive, yet it definitely took us close to three weeks to create our first app on Power Apps, which was mostly SharePoint driven and had pretty decent complexities. It was not a very straightforward application. It took a fairly decent time. It was not a very long-term project, it was short-term, and we could manage to do it in three weeks.
We have not found it difficult to maintain Power Apps. It's pretty straightforward. We haven't had any challenges so far.
What about the implementation team?
Everything was handled in-house.
What's my experience with pricing, setup cost, and licensing?
Right now, we are using an enterprise license without the premium connectors at this point. For Power Automate, we are definitely going to need some licenses which we're exploring.
Depending upon the user requirements, we're still exploring the licensing requirement. Most of the applications that we leverage are without any cost other than the normal license which we are paying for as part of Office 365. We'll take additional licenses depending on the solution and the need.
What other advice do I have?
We have performed a lot of other projects on the Power platform, which is a Microsoft product. So we have used Power App and Power Automate to do many of our automation initiatives.
We are working with the latest version of the solution.
I'd advise potential new users to have the UI designed well in advance. Articulate the flow in which you want to create your Power Apps so that you can save time. Then, do a dry run using Excel as well. It's important when you're using Power Applications, to have your UI design and the BRD clearly articulated, otherwise it might take a little longer to implement Power Apps. Once you have everything in readiness, it will be easy.
I'd rate the solution eight 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.
Power Platform Advisor and Head of Power Platform Team at a computer software company with 501-1,000 employees
Reasonably priced with great features and helpful support
Pros and Cons
- "It uses a lot of AI, which is helpful, especially during the setup process."
- "I would like to see more improvement, for example, in direct collaboration."
What is our primary use case?
I use it for internal purposes and also to advise our customers.
What is most valuable?
Everything that includes PowerApps is very interesting, especially the late editions in direction and mixed reality.
The way you create applications and the nature of language processing are great. The ideas feature that has been added lately has been wonderful. All these types of additions are really cool.
It's a stable product.
It uses a lot of AI, which is helpful, especially during the setup process.
The pricing is reasonable.
Technical support is good.
What needs improvement?
I'm looking forward to further improvements of what you can do with mixed reality capabilities.
I would like to see more improvement, for example, in direct collaboration. There is something currently, however, it's still on a preview mode. I'd like to see more.
What I'd also like to see is to be able to use, for example, another tool for sketching mock-ups or the design of the applications and being able to transport the sketches directly into, let's say, a PowerApps container so I can design the app somewhere else, and then I can transport everything in PowerApps designer, and I can get started with inserting logic in the mock-ups that I have already designed somewhere else. This is something that I'd really like to see in PowerApps.
The experience could be a bit better improved and be consistent throughout all parts that form components. For example, the same experience we have in PowerApps is something that should also be in other PowerApps platform products.
In general, the environments in the workspaces are a bit faster than in the cloud.
For how long have I used the solution?
I've been sung the solution for two to three years.
What do I think about the stability of the solution?
It's a stable product.
What do I think about the scalability of the solution?
We have 200 to 300 people using the solution currently.
How are customer service and support?
Technical support depends on what channels you communicate through, however, largely, we are satisfied.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
This is the first general code solution I'm using.
How was the initial setup?
The initial setup is AI-infused. If you start working on an application, AI works for you in the background and tries to provision everything you need. I would like it to be a bit faster. Sometimes the designer just breaks and you get an error notification.
What was our ROI?
I've seen ROI and I would rate ROI at three and a half out of five, however, I would like for Microsoft to think of ways where we as partners are better supported to have a higher return on investment.
What's my experience with pricing, setup cost, and licensing?
The cost is fair, based on everything you get. I'd rate it at a four out of five as I see that the customers raise constraints. They sort of say it's a bit expensive. I don't know how expensive the other platforms are, however, from what I heard, it's a fair price for PowerApps considering what it comes with.
Which other solutions did I evaluate?
We did not evaluate other options. We are a Microsoft gold partner and for us, the journey was set as we were using Dynamics 365 CRM systems, which basically had PowerApps. It was pretty clear from the outset that we were going in the direction of PowerApps.
What other advice do I have?
I'm a team lead for the PowerApps platform in general and PowerApps is the product of the platform. I'm not sure which version of the solution we're using.
I'd advise others to start with a short hands-on evaluation so that you understand what it looks like when you create on the platform. That will give you a feeling about the components. You get a feeling about what the platform offers and can build slowly up from there. The best way would be perhaps to seek support in the beginning, for example, from partners. If you decide that PowerApps is the way, then consider governance from the beginning on.
There's always room for improvement, however, I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Data Architect at a manufacturing company with 10,001+ employees
Pretty good support and useful for real-time feedback
Pros and Cons
- "We get feedback on a real-time basis, which is actually very useful for us."
- "It is not enough user friendly. It also doesn't integrate very well with SQL Server."
What is our primary use case?
Our sales reps use it in the field on a daily basis. I get the data from there and then analyze it for my needs. We are also developing an application to start using Microsoft PowerApps. I would assume we have the latest version.
What is most valuable?
We get feedback on a real-time basis, which is actually very useful for us.
What needs improvement?
It is not enough user friendly. It also doesn't integrate very well with SQL Server.
For how long have I used the solution?
I have been using this solution for almost a year and a half now.
What do I think about the stability of the solution?
I would say, overall, it is not bad.
What do I think about the scalability of the solution?
We haven't gone that far yet, so I'm not sure. We have almost 500 sales reps who use it.
How are customer service and technical support?
They are good. We get a pretty good response and support from them. I had to talk to them on a couple of occasions, and it was a good experience. I would rate them a nine out of ten.
Which solution did I use previously and why did I switch?
We didn't have anything before.
How was the initial setup?
The initial setup was straightforward, but if you want to put more options, it gets complicated.
What other advice do I have?
It is definitely a useful product. I would absolutely recommend it.
I would rate Microsoft PowerApps an eight out of ten because there are still some issues that we are addressing, specifically related to its integration.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Head of Software Engineering Department at a tech services company with 51-200 employees
A good data development and connectivity tool, that would benefit from a longer period of availability for historical data
Pros and Cons
- "We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms."
- "We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days. We would prefer to be able to offer our customers an infinite amount of history to search."
What is our primary use case?
We use this solution to integrate our apps, and send processed data via the different connectors it provides.
How has it helped my organization?
This solution has allowed us to offer our customers to integrate with our platform platform to send documents, and for them to be processed with a digital key network solution, without having to use the platform directly.
What is most valuable?
We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms.
What needs improvement?
We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days. We would prefer to be able to offer our customers an infinite amount of history to search.
For how long have I used the solution?
We have been using this solution for nearly a year.
What do I think about the stability of the solution?
We have found this to be a generally stable solution, and have only experienced issues when there are a large amount of registers involved.
What do I think about the scalability of the solution?
This is a very scalable solution.
Which solution did I use previously and why did I switch?
We did not previously have a single solution, but instead we used a component that worked using Java. We switched to this software because it was less complex to maintain.
How was the initial setup?
The initial set up of this solution is fairly straightforward.
What about the implementation team?
We implemented this solution using our in-house team.
What's my experience with pricing, setup cost, and licensing?
We would advise organizations that this solution has a high-price point. However, the cost is justified for how comprehensive the package is, and all components of the solution are available under the standard license plan; there are no hidden costs involved.
What other advice do I have?
We would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Business Consultant at a tech services company with 501-1,000 employees
Easy to use with good speed and very good design capabilities
Pros and Cons
- "Overall, the tool is very democratic. It's easy for anyone to use. You don't have to be a professional or well-versed in technology."
- "It's sometimes hard to import groups of options. At this point, I need to enter those manually and it slows the process down."
What is most valuable?
The solution is really strong. I'm not an engineer. I'm an economist. Even without being an engineer, I can handle working with the data warehouse. It offers good speed and excellent design.
If I want to process for payments, I can do it fast and easy in Power Apps. If I need to process information from Facebook, from Twitter, or other places, it's really wonderful.
Overall, the tool is very democratic. It's easy for anyone to use. You don't have to be a professional or well-versed in technology.
What needs improvement?
For me, it's easier if I have visual references in order to learn the system. However, I'm also Spanish, and the tool is in English. That's one level of difficulty. Another level is that there aren't too many Spanish use cases and examples. It would help if there was more documentation in my native language to help me learn the system more effectively. In English, I don't think this is necessarily a problem. There seems to be a lot of English documentation.
It would be helpful if there was more explanations built right into the solution's interface so that I can understand what action is supposed to get what result.
In terms of usability, when I tried to make an amortization table, I couldn't find an exponential option. I don't know if it's ideal for financial tools that deal with credit or loans. I'm still looking into this.
It's sometimes hard to import groups of options. At this point, I need to enter those manually and it slows the process down.
For how long have I used the solution?
I've only been using the solution for about four months at this point. It hasn't been too long. I've used Power VA, Power Pivot, and Power Query for a long time, however, in terms of Power Apps, it hasn't been nearly as long.
What do I think about the stability of the solution?
The tool is good for work. I haven't had issues with bugs or glitches. It doesn't crash.
What do I think about the scalability of the solution?
For me, and the way I am using it, the tool is fine. I'm unsure if it would work on a very large scale for big, big companies.
How was the initial setup?
The initial setup was not complex. It's very easy as it's on the cloud. You don't need to be an expert in order to deploy it.
What's my experience with pricing, setup cost, and licensing?
I'm using a trial version right now. I'm still learning the system, so I haven't moved into a paid version yet.
It's my understanding that the pricing isn't too bad. I've heard other people mention it's not as expensive as Azure in comparison with Linux. One or two licenses may not be too expensive, however, I don't know the exact pricing.
What other advice do I have?
I started working with the common data model and the entities and working with my data warehouse. Now I'm working on my data warehouse with common data series. I use Power Apps for my standard entities' values. I need to modify it now with the new processes that are in place. And in the beginning, I use Power Apps for the management of the entities for Power VA. Since I've started using Power Apps, as I can see it's powerful and makes it easy for many, many, many kinds of work processes.
I'm still trying the solution out, and I'm still learning a lot about it. I'm by no means an expert yet.
I'm pretty satisfied with the product. Overall, I would rate it eight out of ten. It's a good tool and it's nice that it's part of a suite in Microsoft.
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Founder & CEO at Logesys Solutoins India Pvt Ltd
Reliable and issue free with helpful technical support
Pros and Cons
- "The solution is stable and reliable."
- "We'd like to see more integration capabilities in the future."
What is our primary use case?
We use it as part of our analytics offering. We are basically into analytics. Maybe sometimes we use it to build small apps to instrument the research process. That's what we do.
What is most valuable?
I am from the sales side, so I really do not know the technical aspect of it.
It's my understanding that it has been issue-free.
We have pretty easy integration options.
Technical support is great.
The solution is stable and reliable.
The scalability is good.
What needs improvement?
I don't have any notes for improvement. It does what it says it does.
We'd like to see more integration capabilities in the future.
For how long have I used the solution?
We've been using the solution for about three years.
What do I think about the stability of the solution?
The solution works well. It's stable. the performance is good. there aren't bugs or glitches and it doesn't crash or freeze.
What do I think about the scalability of the solution?
We use it for a very specific purpose, and therefore scalability is not really a factor for us.
We have about ten clients using the solution currently.
How are customer service and support?
Technical support has been fine. We are satisfied with their level of service.
How was the initial setup?
We use the cloud version of the solution. There isn't an in-depth deployment process.
What about the implementation team?
We handle the projects and the implementation for our clients.
What's my experience with pricing, setup cost, and licensing?
I don't have any comments on the cost or licensing. It's fine. It's cheap compared to other RPA tools. It was about $40. There are people that are lower than that, however, they don't give you the features.
What other advice do I have?
We use a lot of Microsoft products. We use Microsoft Power BI, Power Platform, and Azure Patch Solutions.
I'm not sure which version of the solution we're using.
I'd recommend the solution to others.
I would rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
ServiceNow
Pega Platform
Oracle Application Express (APEX)
OutSystems
Salesforce Platform
Microsoft Azure App Service
GitHub CoPilot
QuickBase
ServiceNow Now Platform
HCL Domino
Oracle Visual Builder Cloud Service
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Would you choose ServiceNow over Microsoft PowerApps?
- Would you choose Microsoft Azure App Service or PowerApps?
- What are the key factors to select between low-code platforms: Microsoft PowerApps vs ServiceNow?
- Which app builder do you use in Microsoft Power Apps and is it worth paying for?
- Is Microsoft Power Apps for businesses or for developers?
- How suitable is Microsoft Power Apps for complex applications?
- How would you choose between Microsoft PowerApps and Salesforce Platform?
- Looking for recommendations for a no-code backend database for 500,000+ users - looking at CASPIO
- Help to migrate IBM Lotus Domino to another platform
- When should you use rapid application development and what are the most suitable projects for it?