Microsoft Power Platform Low-Code Services
View All Tags
You're creating a SharePoint environment variable in a Power Apps solution, you've typed its name, and you have no SharePoint connection yet. You choose + New connection, and Power Apps asks Are you sure you want to discard changes? Discarding throws your form away, and no connection page opens. The fix is to do things in a different order.
You open a solution in Power Apps and a yellow bar across the top says One or more commands are unavailable due to your current privileges for this environment. Nothing is broken. Your Dataverse security role simply doesn't allow some of the solution's commands, so Power Apps hides or disables them.
You've just added Dataverse to your Power Platform environment, opened Solutions in Power Apps, and instead of a list of solutions you get We couldn't load your data. Try again doesn't help. The cause is a missing security role, and in the Default environment it usually fixes itself within minutes.
Every screen of the Career Development Plan app reads from or writes to two SharePoint lists. This part builds them, and the site they live on, column by column and setting by setting, exactly as the app will expect them.
Plenty of teams still track career development in spreadsheets: which skills each role needs, how far each person has got, and who has signed it off. This series replaces that with a Power Apps app. Each person sees the competencies their role expects and writes a short response for each one. Their manager then approves or declines it, all on SharePoint and the Microsoft 365 licenses you already have.
Power Apps keeps numbers the way a calculator does — 123456.789 — but the people using your app expect to read 123,456.79. The Text() function converts a number or integer to text and formats it in the same step, as long as you know the one situation where it silently does nothing.
Sooner or later a flow needs to find a person — the manager to notify, the owner of a request, the account behind an email address. The Search for users (V2) action from the Office 365 Users connector does exactly that: give it part of a name or an email address and it returns every matching Microsoft 365 user.
Power Automate is strict about data types. If you try to concatenate a number into a message, save it into a text column, or pass it to a connector that expects text, the flow fails with a type mismatch. The fix is the built-in string() expression, which converts a number or integer into its text or string representation.
