Read First: Customization Recommendations

Introduction to Solution Customization

Solution customization primarily refers to any change to a solution object that can be moved within a custom solution to another Power Platform environment. While there are many customization options available within a Microsoft 365 Power Platform environment, there are guidelines that are recommended when working with a managed solution such as BrightWork 365, particularly due to how these affect future solution upgrades. Our guidelines will help you understand the recommended approach to take if you decide to make changes to components of the out of the box solution. You also have the option to reach out to  your assigned Customer Success Partner or support365@brightwork.com with any upgrade concerns you might have.

We strongly recommend working alongside a BrightWork Customer Success Partner to customize components within BrightWork 365. See the Deployment section for more information.


Managed and Unmanaged Solutions

The Microsoft Power Platform uses solutions to implement an application lifecycle management process. There are two types of solutions: unmanaged and managed.

Unmanaged solutions are primarily used in development environments when changes are still being made to an application. With unmanaged solutions you can:

  • Add and remove components.
  • Export the solution.

Managed solutions such as BrightWork 365 are fully developed and are intended to be distributed, installed and used for production purposes. The following are attributes of managed solutions:

  • Components cannot be added or removed.
  • Managed solutions cannot be exported.

Although customers can make certain configuration changes in a managed solution as noted in the Configuration Knowledge Base category of articles, customization changes must be made in an unmanaged solution.

Customizations should only be made in an unmanaged solution, not a managed solution. For additional information contact your Customer Success Partner. 

For more information from Microsoft see Solution Concepts


BrightWork 365 Solution Components

The solution editor screen displays a list of solution components relevant to BrightWork 365.


Recommended Process for Component Customization



  • You will need to be at least a Power Platform System Administrator to be able to perform component customization.
  • Content data is not copied into environments when importing solutions.
  • If you decide to modify solution components, we advise that you follow Microsoft's recommendation to have separate Dev and Test Power Platform environments, in addition to your Production environment. See Create Environment.
  • If a BrightWork 365 upgrade contains updated elements that are associated with components that have been previously customized in an unmanaged solution of yours, such as a new tab section on a form, etc., these new elements will need to be manually applied to your unmanaged solution; this is in addition to the import of the BrightWork supplied managed upgrade solution. Contact your Customer Success Partner for more information.
  • It is important to be aware of the implications of hiding or deleting key fields and the effects this can have on other areas of the app, for example the effects of hiding the Issue Status column on various views, charts and Power BI. Contact your Customer Success Partner for more information.
  • We recommend not making any changes to the "Default" solution in your BrightWork 365 environment as this will likely cause technical issues.

First Time Setup Process for Component Customization

  1. Install the same version of BrightWork 365 that is installed in your Power Platform Production environment as a managed solution in your Dev and Test environments.
  2. In the Dev environment, create a clean unmanaged second solution. See Create Solution. This unmanaged solution is necessary because components should not be modified in a managed solution. It is also not recommended to create an unmanaged solution in a Production environment. See Understand How Managed Solutions are Merged.

Ongoing Process for Component Customization

In your Dev environment, in the clean unmanaged solution previously created:

  1. Add new objects (e.g. Project Form) and any specific existing BrightWork 365 components requiring modification - do not choose All Components when adding components, and add only those specific elements needed for your customization in order to keep the unmanaged solution as clean as possible.
  2. Modify the added components as necessary - see the various customization Knowledge Base articles.
  3. Export your modified solution as a managed solution. See Export Solutions.

In your Test environment:

  1. Back up the current BrightWork 365 solution.
  2. Import the managed solution that contains your modifications using the same account that was used to install BrightWork 365; this new imported managed solution will be layered with the original installed BrightWork 365 managed solution.
    Note: Only users with a Power Apps per User license should perform a solution import.
  3. Import any new custom forms and templates. See section "Import Forms and Templates" in the BrightWork 365 Install Guide.pdf
  4. Test the functionality of the BrightWork 365 app with the modified components before proceeding to your Production environment.

In your Production environment:

  1. Back up the current BrightWork 365 solution.
  2. Import the managed solution that contains your modifications using the same account that was used to install BrightWork 365. This new imported managed solution will be layered with the original installed BrightWork 365 managed solution.
    Note: Only users with a Power Apps per User license should perform a solution import.
  3. Import any new custom forms and templates. See section "Import Forms and Templates" in the BrightWork 365 Install Guide.pdf