Power Platform Booster is in public preview. Documentation will always reflect the latest version.

Power Platform Booster has 5 mechanisms implemented to optimize API requests:

  • “To process” lists for canvas apps and cloud flows.
  • Top count variable.
  • Manually enable an environment for processing
  • Manually enable a canvas app/cloud flow for clean-up
  • Caching in the canvas app “PP Booster – Admin – Clean-up”

Besides these mechanisms, a SharePoint throttling mechanism is also implemented. More on this can be read here.

“To process” lists for canvas apps and cloud flows

Canvas apps

The cloud flow “PP Boosters – Apps to process” collects data of all canvas apps of enabled environments. This data is stored in the list “Apps to process”. The cloud flow “PP Booster – Apps” reads per run a maximum number of items from this list. This maximum is based on a setting (appstopcount) and this way, the amount of API requests per run can be influenced.

See page How to use Power Platform Booster for more information.

Cloud flows

The setup described at “Canvas apps” is also implemented for cloud flows only then with other cloud flows (related names).

Top count variable

The following cloud flows also have a maximum number of items retrieved per flow run:

  • PP Booster – Apps
  • PP Booster – Flows

This maximum is configured with the following settings:

SettingDescription
appstopcountThe number of items to retrieve at a maximum per flow run. This setting is used in the flow:
*) PP Booster – Apps
flowstopcountThe number of items to retrieve at a maximum per flow run. This setting is used in the flow:
*) PP Booster – Flows

Manually enable an environment for processing

The cloud flow “PP Booster – Environments” collects data about all environments the PP Booster account has access to and stores it in the list “Environments”. One of the fields in this list is called “Process”. This field determines if the flows “”PP Booster – Apps to process and “PP Booster – Flows to process” use that environment for processing.

Manually enable a canvas app/cloud flow for clean-up

Canvas apps

The list “Apps” has a field called “No clean-up”. This field determines if that app is processed by the flow “PP Booster – Clean-up apps”.

The default value is “True” meaning that that app is not processed for clean-up. The value must be manually changed to “False”. A date in the field “Clean-up date” must be selected for the processing mechanism to work. When the clean-up date is prior than the moment the flow “PP Booster – Clean-up apps” is executed, a clean-up task will be created for that app.

Cloud flows

The setup described at “Canvas apps” is also implemented for cloud flows only then with other cloud flows (related names).

Caching in the canvas app “PP Booster – Admin – Clean-up”

The canvas app “PP Booster – Admin – Clean-up” has an active button for the card/action “Apps to delete” called “Shared with”. When this button is clicked, the account with which the canvas app is shared is retrieved and stored in a collection. When the button is clicked again, the values in that collection are used. This caching mechanism is reset when the screen is loaded (OnVisible property of related screen).