The Baretta

 What How to give a Power Platform Administrator the System Administrator rights so that you have full control over your default environment. Why By default, no one has access to create a new table/entity in the Dataverse in the default environment.  In our instance, we are extending the capabilities of Microsoft Planners Premium Plan Metadata. How The normal methods of going into the PP Admin Centre and giving yourself 'System Administrator' rights is disabled.  The only way to give yourself full admin access is via the 'Membership' button found here on the homepage of the Environment Administration for the default environment.

What Providing you, a Power App developer, with the steps to quickly apply theming and naming conventions to all fields within your app, by utilising any GenAI tool. Why After a swift session of adding labels and text boxes and such to your app, and nicely theming one, but then having to apply all the values to other fields, your app probably looks something like this.   At this point, if you are like me, your next steps are: clean up field names re-order tree-view from top to bottom ensure theming matches throughout Depending on the complexity of the app, doing a good job of this could take a whole day. How Add all your fields to your app Theme one perfectly 'View Code' on the Screen and Copy the YAML to Notepad   Open up your preferred GenAI tool - for this exercise I'm using  https://claude.ai/   Enter the following Prompt, before pasting in the code you copied from step 3: I've just built a Power App, but need your help with the following: 1. Naming fields approp...

What Environment Variables are a great way to manage your solutions as they pass through DEV/TEST/PROD environments.  They save having to manually update flows/apps during each change and test iteration. However there is a gotcha to understand when you're planning your next migration or app update. More on Environment Variables | Microsoft Learn Why The two issues I faced using Environment Variables were due to the ' Current Value '. Issue #1 : If you don't want the value you used in DEV to push through to TEST/PROD, you need to remove the 'Current Value' from your solution BEFORE exporting it. If this is not done, and you're migrating as a  managed  solution, the 'Current Value' will flow through to your TEST environment, and cannot be changed because the solution is locked down. When a single sentence in an MS Learn article can cause so much pain... Issue #2 : If you're like me and you realised this AFTER you'd already imported into another...