You’re offline. This is a read only version of the page.
34
Good day everyone,
I'm not sure where this question fits in the forum, it's between Power Pages and Power Apps.
Let's use the example of a Power App that allows you to process requests from customers. You design a simple model-driven application to do so, basically forms and business processes.
After the application is built, you're asked to create a web interface so customers can send the request online. That's the part where I'm a little bit confused about what to create and what licenses are required to get it running.
If you want to set up a whole authentication system so customers can create and manage their requests, I guess that's where a Power Pages is really required. But if you have like 5000 customers, the pricing will go overboard. And if it's just to create and manage simple requests, this seems to be overkill. Am I looking at the right thing ?
And what about you don't really need the user to completely authenticate, but only confirm that you have them in your database so the contact fields are filled automatically, what option is there to do that ?
And finally, if you only want an online form where users don't need to authenticate to send a request, do you go with an anonymous pricing ? That seems to get pricey fast.
--
I hope you understand what I'm asking in this post. When should you go with a Power Pages and what other option is there. Some organization has only a small volume to handle, so they don't want a pricey website. Other organizations have a lot of customers, so the prices can go overboard. What am I missing, or is it the way it is ?
Thanks for your time.
Share
Report
All responses (
Answers (
