Branding Template App V3 09-17-2019 17:24 PM - last edited 03-18-2023 04:22 AM

[iAm_ManCat]

(if you downloaded this before Feb 2nd 2022, please re-download!)

This template will allow you to customize your theming (down to the control-level), and allows you to theme items that are not currently possible within the normal Power Apps Editor!

There are also accessibility tools available within it that allow you to change your theme to an accessible theme or to change your font size on-the-fly.

If you want to read the full write-up on V3 of my Power Apps branding template, please feel free to view this on my site (although reading that is not required to download it at the bottom of this post, I do recommend it!):

https://www.iammancat.dev/2022/01/power-apps-branding-template-v3/

If you just want to download the template, you can download it at the bottom of this article 🙂

Cheers,

Sancho Harker (iAm_ManCat)

[

If you want to edit your existing App to do granular edits to the .json files inside, extract it to a folder, do your editing, and then run the following powershell script (within this repository) from within that extracted folder after you've done modifications, which will reconstitute it into a .msapp file:

https://github.com/iAmManCat/PowerApps-Branding-Template/tree/master/V3 

]

[MichaGue]

Hello Sancho,

after adapting your template to my needs and creating several apps with it, I am wondering how I can use the components created in the apps more sustainably and update further developments of the components in other apps.

I have a master application as a starting point for new apps. This master application contains components that, for example, facilitate the use of a header or navigation.

=>Master_Template (based on Branding Template App V3)
==>Master_Component_Header_Version_1
==>Master_Component_Navigation_Version_1

Based on this master template, I am developing a new application. In the course of time, the components contained in the master template will be extended with new functions.

How do I now manage to take over the updates of the components in the master template in the already existing applications?

Attempt 1: Use the import/export function for components in the app (even if it is phased out - currently retired).

Problem: When importing the updated components from the Master_Template, the existing components are not updated, but a new component is created. As a result, the entire app has to be updated manually.

Attempt 2: Using a component library in Power Apps

Problem: The global variables used in the components of the Master_Template are not defined in the component library. Importing this component library into an application based on the master template does not solve the problem either.

Question: Do you have a solution for updating the components without having to rework the entire application?

Many thanks for your tips.

Greetings Michael

[iAm_ManCat]

Heya @MichaGue, yes I do!

I would suggest using a component library, and everywhere that you are using a global variable I would instead use a passed-in Input value of whatever type you need, then when you insert the component you can replace the default input values with the global variables you have from that App - this ensures they are passed in as inputs rather than needing to reference the variables directly from the component 🙂

Cheers,

Sancho

[Lateef01]

This is absolutely great.

[MichaGue]

Hello @iAm_ManCat,

thank you for your recommendation. I have taken a closer look at your solution and implemented it in a small test. With the goal of making this template I customized available to others in my organization attached is my personal evaluation.

Advantages:

• Updates in the central library are shown in the app and the user can decide if he wants to update his app.

Disadvantages:

• The number of global variables used is already relatively large for small components. My test with a simple footer came to a use of >30 global variables.
• When using a component from the library, the default values of the component's inputs have to be exchanged with the global variables used in the APP. This is not very user-friendly and time-consuming. This must be done again and again, as long as one takes over a component from the library. It can be avoided with already used components in the APP, in which one copies these.
• Another disadvantage is that the library must be shared. That means, if one would like to make the Template available within an organization, everyone, who would like to use it inclusive the library, must receive the access rights to the library. This seems uncomfortable from an organizational point of view.

It would be ideal if one could simply update the template made available for download including the included components.

@iAm_ManCat 

Do you have any experience with using Github and Power Apps. Could you update the components via this, in which you extract the files of the components from a new version of the template and update them via Github?

Another option that might work would be to update the components by saving the Power App to the desktop and unpacking it with the known scripts. Do the same with the current version of the app. Can you then simply replace the files of the components, rebuild the app using the script and upload it?

Thanks for sharing your experience.

Many greetings,
Michael

[Amos01]

Great job!

[PeteM3]

Hi Michael

were you able to implement this via GitHub?

Thanks

Pete