Current Status
Not Enrolled
Get Started
This course is currently closed

If you've started learning how to be a Citizen Developer, the chances are you've built one or more PowerApps. With the power at your fingertips that the Power Platform offers, it's easy to get started and simple to create super-powerful applications that help your business processes. 

Apps that look great and function as you need are only part of the story. It's equally important to think about how to change your PowerApp or provide support in the future. 

Using some good practice tips in this playbook, you'll learn about 3 ways to configure key properties and help make your PowerApps :

  • Easy to re-brand
  • Simple to adapt to a different look and feel
  • Quick to support and update in future 

There are multiple ways to create re-usable configurations when using PowerApps. You can : 

  • Create properties on your controls that you reference within other screens
  • Create variables that run when you start your PowerApp and reference them within your screens. 
  • Create components  and bring these into your screens (at the time of writing this is in preview)

In this playbook, we'll focus on the first and second options and give you two examples to use when creating a re-usable PowerApps configuration. We'll focus on 6 common properties you'll want to change in the future to get you started. 


You may also like

test Rest API post

test Rest API post

test Rest API post

test Rest API post
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

Get in touch

0 of 350