Frequently asked questions, tips and how to's

This article will provide you with answers to frequently asked questions and tips on setting up and using the CoE Starter Kit.

Installing a solution in a Production Environment

  1. Go to make.powerapps.com.

  2. Go to your CoE environment. In the example in the following screenshot, we're importing to the environment named Contoso CoE.

    Power Apps maker portal environment selection.

  3. On the left pane, select Solutions.

  4. Select Import, and then Browse.

  5. Select the solution from the CoE Starter Kit download.

  6. Establish connections to activate your solution. If you create a new connection, you must select Refresh. You won't lose your import progress.

    Establish connections to activate your solution.

  7. Update environment variable values. The environment variables are used to store application and flow configuration data with data specific to your organization or environment. This means that you only have to set the value once per environment and it will be used in all necessary flows and apps in that environment. Update environment variable values.

  8. Select Import.

Installing a solution in a Dataverse for Teams Environment

  1. Select the Microsoft Teams group you want to add the solution to.

  2. Install the Power Apps personal app in Microsoft Teams

  3. Create your first app (at least one app is required in the environment to enable the solution import experience).

  4. Open to the Power Apps app in Teams, select Build, and select the Team you want to add the solution to.

  5. Select See All

    Open the Power Apps app in Teams to import a new solution.

  6. Select Import

  7. In the pop-up window, select Choose File.

  8. Select the solution from the CoE Starter Kit download.

  9. When the compressed (.zip) file has been loaded, select Next.

  10. Establish connections to the required connectors, If you create a new connection, you must select Refresh. You won't lose your import progress.

    Establish connections to all connectors used in the solution.

  11. Update environment variable values. The environment variables are used to store application and flow configuration data with data specific to your organization or environment. This means that you only have to set the value once per environment and it will be used in all necessary flows and apps in that environment.

  12. Select Import.

  13. Once the import is complete, your solution will be available by choosing Installed apps. Select See all to see all tables, apps and flows part of the solution.

    Select Installed Apps to view your imported solution.

Set flow run only users properties

  1. Remove unmanaged layers for all flows.

  2. Go to the details page and select the Run only users edit button.

    Find setting for run only users.

  3. You will see all the connections in the child flow. For each one, change the value to Use this connection (userPrincipalName@company.com).

  4. If there is no connection for any of the connectors, go to Data > Connections, and create one for the connector.

    Configure run only users.

  5. Once you have updated all run only users, you can turn on the child flow.

Running a full inventory

The sync flows in the Core Component solution will only update resources that have changed since the last run. After an upgrade, you will only see the benefits of bug fixes or changes when you run a full inventory sync:

  1. Set the value of the Full inventory environment variable to Yes (Learn more: update environment variables).
  2. Turn all flows in Core off and back on (note this step is temporary while we await a fix to a caching bug in flow).
  3. Run the Admin | Sync Template v3 flow.
  4. Set the Full inventory environment variable back to No.
  5. Turn all flows in Core off and back on

Update Environment Variables

The following limitations apply when updating environment variables:

  • You cannot update the values for environment variables from within the imported solution.
  • You need to always add/update a Current value, not the Default value, because the Default value will be overwritten when you install an upgrade.
  • Environment variables are cached in cloud flows until the flow is reset (example: turn the cloud flow off and back on).

To update Environment Variables, you can use the Admin - Command Center

  1. Go to make.powerapps.com and select your CoE environment

  2. Open the Admin - Command Center app.

  3. Select the tool icon and update the current value.

    Update environment variable values in the Admin - Command Center app.

Note

After changing an environment variable value, you will need to turn off and on all flows using that environment variable to make sure the flow uses the latest value.

If you are not using the Admin - Command Center

To update Environment Variables:

  1. If you have installed the solution in a Production environment:

    1. Go to Power Automate.
    2. On the left pane, select Solutions.
    3. Select the Default Solution, and change the filter to show Environment Variables.
    4. Select a variable that you want to update, and then configure its Current Value.
  2. If you have installed the solution in a Dataverse for Teams environment:

    1. Go to Power Automate.
    2. On the left pane, select Solutions.
    3. Select the Common Data Services Default Solution.
    4. Select + Add > Environment Variables.
    5. Select the existing Environment Variables from the managed solution that you want to update.
    6. Now, change the filter to show Environment Variables.
    7. Select a variable that you want to update, and then configure its Current Value.

Share an app from a Production environment

  1. Go to make.powerapps.com and select your CoE environment.

  2. Select ... > Share on the app you want to share.

    Select the user our group to share the app with

  3. Select the Dataverse security role - the CoE Starter Kit makes three security roles available:

    1. Power Platform Admin SR for sharing an app with admins
    2. Power Platform Maker SR for sharing an app with your makers
    3. Power Platform User SR for sharing an app with end users

    Assign a security role to the user or group

  4. Select Share.

Share an app from a Dataverse for Teams environment

  1. Open to the Power Apps app in Teams > Build > Select the team you have installed the CoE Starter Kit in > Share with colleagues. You must be a team owner to see this option.

  2. Search for and select the security group you want to share the apps and tables with.

  3. Select the apps you want to share with members of this security group.

    Search for a group to share apps with

  4. Select Save.

  5. Select Installed apps.

  6. Select See all on the Center of Excellence - Core for Teams solution.

  7. Select Tables from the left pane.

  8. Select the table you want to manage > Manage Permissions.

  9. Assign table permissions to the security group. The level of permission will depend on the app you are sharing. Perform this step for all tables used by the app you are sharing.

    Assign table permissions to your colleagues

  10. To access the app, colleagues with access can go to Microsoft Teams > Apps > Built by your colleagues and select the app from there.

    Find apps in the Microsoft Teams app store

    Note that apps are only accessible from within Microsoft Teams.

Get a Power Apps URL from a Production environment

  1. Go to make.powerapps.com and select your CoE environment.

  2. Select ... > Details.

  3. Select the web link.

    Get the web link for a canvas app

Add apps to Microsoft Teams

  1. Open to the Power Apps app in Teams > Build > Select the team you have installed the CoE Starter Kit in > Installed apps.

  2. Select Apps and select Edit for the app you want to add to teams.

    Edit the app in teams

  3. Select Publish to Teams > Next.

    Publish the app to your Microsoft Teams channel

  4. Select Add to a Channel > Save and close.

    Select a channel to add the app to

  5. If you would like to save the app URL, navigate to that channel in Microsoft Teams, open the app and select Copy link to tab.

    Copy the link to this tab

Timeouts in the Admin | Sync Template v3

The Dataverse connector might experience some throttling limits if the tenant has many resources. If you see 429 errors in the flow run history occurring in later runs, you can try the following resolution steps:

  • Configure the retry policy

    1. Open Admin | Sync Template v3, and then select Edit.

    2. Expand the step Get Environments and store them in the CoE Table.

    3. Expand the step Apply to each Environment

    4. Go to the Settings pane for each call to Dataverse, and configure the timeout/retry settings. The default count is set to 10 and the default interval is set to PT10S - increase the values incrementally here.

      Configure retry policy.

  • Configure (reduce) concurrency in Foreach loops to reduce simultaneous calls

    1. Open Admin | Sync Template v3, and then select Edit.

    2. Expand the step Get Environments and store them in the CoE Table.

    3. Go to Settings for the Apply to each Environment step.

      Configure concurrency in Foreach.

    4. Use the slider to reduce the value of Degree of Parallelism. The default value is 50; reducing the parallelism here will increase the runtime of the flow, so we suggest gradually lowering the number.