PowerFX was only announced officially this year, still feel its too fresh to say one is a "PowerFx developer" proper. And even then, Microsoft is only beginning to roll it out to their other platforms outside of powerapps.
Powerapps, especially when you run through Microsofts official certifications, is definitely touted as just one part of the whole Power Platform, including Power Automate, Power BI and Power Virtual Agents.
From a business/career perspective this also makes sense, in that one shouldn't just be using Powerapps alone in a developer/programming context - it's a suite of products and a tech stack to analyze and solve business problems in a way that is proposed to be quicker than even traditional DevOps. See the vision for Fusion Teams/Fusion development approach.
These are business users (not necessarily developers proper) that know the business "on-the-floor" in other technical capacities but using the tools of the power platform to work alongside pro dev that would put together the APIs, the pipelines, etc.
Knowing other languages is just another part of the Power Platform developer toolset to solve business problems.
Do you use a registered Microsoft license reseller?
If so ask them about bundles, if not go direct to Microsoft and work a deal. At 2k+- users, Microsoft would be more than happy to make a deal. I have 2500 in my org and Microsoft made a nice deal.
Also the pricing cut in half. Now $20 per user per month for premium: https://powerapps.microsoft.com/en-us/pricing/
>Is there any technical skill which I need to learn to incorporate in PowerApps?
Power FX.
Link to Microsoft Power FX page
Hi there! Microsoft offers some training material on how to make apps with Powerapps. I found this training on Udacity which shows how to create apps, and it includes a piece on Power Automate as well:
https://www.udacity.com/course/microsoft-power-platform--ud091?WT.mc_id=twitter-social-donasa
I just created a solution where the sharepoint data source environment variables worked like expected.
You need to follow the steps described in this blog post.
This is actually a pretty complicated aspect of the service, but there are some documents out there about how to set yourself up.
I believe the short answer is that, yes, you will need a license to "run" a PowerApp, even if you aren't the one that built it. Whether that's the trial (as alluded to by /u/kwagenknight) or a paid P1, P2, or another SKU.
The PowerApps pricing page has some stuff about this depending on your scenario.
This licensing overview also talks about things through the lens of O365 trials.
There are two types of connectors: standard and premium. Connectors help you connect with the data source. Standard connectors include excel, onedrive, sharepoint etc. Meanwhile premium ones include SQL Server, oracle and many others. With E3 license you could use powerapps with standard connectors but not premium ones. There are two license: per app and per user.
Let's say you want to use SQL server as your data source to store and load the data. In that case you will require a license model for evey user who uses the app, either per app or per user (depends on your requirement).
This, as for your app each user you share it with will require an additional Premium licence, where as for Cloud flows, only 1 user will require a licence which may work out cheaper
Also this method you can have it send an email to let you know it has ran or even add in approval from you before it runs
Look at this though https://powerapps.microsoft.com/en-us/developerplan/
;)
While this is from 2017 it could help you with your goal:
https://powerapps.microsoft.com/en-us/blog/office-template-onboarding-tasks-now-available/
Here is a link that is more recent that also covers what you are trying to do. Plus it has an physical example you could look at.
https://www.knutrelbemoe.com/post/hr-onboarding-powerapps-sample
The transition parameter was required, but the requirement was removed last month - see https://powerapps.microsoft.com/en-us/blog/more-small-steps/ for the announcement.
I'm also a newbie but someone on this sub recently posted a link to this free power platform course:
https://www.udacity.com/course/microsoft-power-platform--ud091
The exercises teach you how to create a canvas app similar to what you're talking about. I had a great time working through this course.
Dataverse for Teams is free, might have to look up the limitations compared to "real" Dataverse thou.
I already built apps within DV4T, but it's not really as nice an experience as working with the native PA designer.
If you have 15 people working with the data, you need to consider the cost for 15 premium licenses:
https://powerapps.microsoft.com/en-us/pricing/
Working with 15k items in SPO would not be the big deal, it all comes down to how you filter the data. Delegation is depending on funkctions, f.e. Search is delegated using SPO, not with Dataverse.
Filter is fine with both sources. So if you manage to filter down your data to a result below 2k, you are fine.
If I move apps from one place to another, I use the VS Code extension to edit the .msapp file directly.
https://powerapps.microsoft.com/en-us/blog/power-platform-extension-for-vs-code/
This helped me a ton lately and saved hundreds of hours, maybe it can do the trick for you.
This was my exact experience as well. You are definitely not alone. We were looking for a no code / low code platform where departments could stop "managing by spreadsheet" and create centralized apps to become more productive and efficient. PowerApps wasn't even close to satisfying that need.
Bubble.io has been good so far, but we're still in the POC phase.
The main benefit is to have source control also outside of Power Apps. It also uses the canvas source code tool Microsoft announced a while back. Which means you will be able to read all the formulas you write in the source code system without having to open Power Apps (https://powerapps.microsoft.com/en-us/blog/canvas-source-code-tool-integrated-with-power-platform-cli/)
Could a Portal work in this instance?
This further article provides some abstract examples of this method https://powerapps.microsoft.com/en-us/blog/bulk-update-using-forall-and-patch/
I've implemented this kind of approach by using a collection that exactly matches the column names of the data source Im updating. It took me a while to get it all working (can't remember why as I probably subconsciously try to forget these sort of annoying issues with power apps).
Some more practical examples in this blog post: https://matthewdevaney.com/patch-multiple-records-in-power-apps-10x-faster/
Take a look at the documentation for the recently upgraded Container control:
Seems like it's basically flexbox under the hood.
Have you tried setting up a free personal aka developer powerapps environment? Its comes with cds just has a size limitation but perfectly functional. Only caveat is that you can't share apps with others but perfect for using it yourself and developing apps to export to other sandbox or production environments. Its called the powerapps community plan see here to sign up: https://powerapps.microsoft.com/en-us/communityplan/
There is a way to do this, but I’m not somewhere that I can open my Powerapps to get at how I have it set up. Hopefully this article helps:
https://powerapps.microsoft.com/es-es/blog/separate-custom-forms/
CDS internally requires a licence yes. Minimum is the per app / per user licence. It costs about $10 per user per month. It gives access to 2 apps and 1 portal and power automate flows (included premium features) which are connected to the apps.
Portals is an add on.
This is entirely possible and is a great use case for Power Apps.
There is a fantastic blog post with learning resources for Power Platform at https://powerapps.microsoft.com/ro-ro/blog/microsoft-powerapps-learning-resources/
Don't forget, you get 2! apps for the $10/user/month. Once you get to 5 apps, it's cheaper to run the unlimited $40plan.
https://powerapps.microsoft.com/en-us/pricing/
My poor vacation request plan was going to cost $60k/year to implement. A consultant dev and 2 months time cost $20k with $5k for infrastructure AND we don't have to pay that again the next year, or the next, or the next. My ROI was 5 months, so it was an easy sell to the bean counters. Even if we have to bring someone back in for updates, etc, we come out way ahead for building a few apps here and there.
For 100 users, the ROI would just be over 2 years with a similar cost which may make the buy/hire/papp it decision a bit harder to sell. Month 26 it's free though. :)
You can pretty much do the same thing, but it is a little different with powerapps. You add the parameter at the end of the URL, but you need to add some code and a timer to the PowerApp. You set the time to autostart, and at the end of the timer run you set some code to check for the parameter in the url and if the parameter exists it will run a Navigate() function to navigate to the screen you want. If the parameter does not exist then nothing happens. It's a little clunky, but so far its the only way I found to do it. Here's the link to some info on the MS site with more details:
​
https://powerapps.microsoft.com/en-us/blog/powerapps-deep-linking/
You can try exporting as Zip file, you have to fix broken connections after the import but other than that it should work.
Here is a reference:
https://powerapps.microsoft.com/en-us/blog/powerapps-packaging/
Well you already have Power Apps and Power Automate licenses for O365 as part of your E1. That should cover all standard connectors. Are you working with premium connectors that require premium licensing?
Here's a cost guide for premium. https://powerapps.microsoft.com/en-us/pricing/
However you can setup a flow to notify the users about the rules, best practices, training videos... if the user didn’t accept the rules the same flow can delete the recent created app. I would like to recommend reading this blog post about CoE Kit: https://powerapps.microsoft.com/en-us/blog/update-to-the-power-platform-center-of-excellence-starter-kit/
And also this one: https://powerapps.microsoft.com/en-us/blog/establishing-an-environment-strategy-for-microsoft-power-platform/ about the environment strategy. For new environments you can control who has right to create apps.
MS has a whitepaper for governance and deployment: https://powerapps.microsoft.com/en-us/blog/powerapps-enterprise-deployment-whitepaper/
They are correct, sort of. The 50mb for plan 1 is the amount allocated per license. Storage is pooled at the tenant level. So if you have 10 plan 1 licenses, thats 500mb. There is a comparison of both plans here https://powerapps.microsoft.com/en-us/pricing/
I believe they have updated choice fields to be delegatable, so this should work the way you've described.
I believe the syntax would be filter('helpdesk', status.value="WIP")
https://powerapps.microsoft.com/en-us/blog/sharepoint-delegation-improvements/
The office side of the app is definitely possible, but PowerApps currently can’t be shared externally from your environment. :(
The new PowerApps Portals will likely do what you need but it’s still very much in preview and lacks basic features. https://powerapps.microsoft.com/en-us/blog/introducing-powerapps-portals-powerful-low-code-websites-for-external-users/
E3 and F1 licenses will be able to use standard data con ections within powerapps. Azure SQL is moving from standard to premium.
>Based on the scenario that you mentioned (an canvas app using Azure SQL and SharePoint List as data source), I afraid that you would not be able to develop and distribute Apps. Effective October 1, 2019, the Azure SQL connector will be reclassified from Standard to Premium. If you want to access all Premium, on-premises and custom connectors within your PowerApps, you must purchase a standalone PowerApps or Flow plan license.
https://powerapps.microsoft.com/en-us/blog/new-licensing-options-for-powerapps-and-flow/
Check out the relatively new PowerApps Portals. This may get you what you are looking for.
It may not be rolled out to your environment yet.
https://powerapps.microsoft.com/en-us/blog/tree-view-has-an-app-item-to-make-app-building-easier/