You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The goal is to enable impact analysis for apps that use PCF components. The scenario is that an environment has PCF components enabled, and an admin may want to disable that - we then want to run an impact analysis to show which apps are using PCF components.
This information is available in new properties that have recently been added to the Get Apps as Admin output, in the appDocumentComplexity scope:
Either if pcfControlCount > 0: store a true/false in a new field of usesPCFControls
OR (probably better option)
If we think we will use the appDocumentComplexity attributes for other purposes, such as showcasing complexity of an app (which could be relevant reporting), we could store pcfControlCount as a number (and then the reporting would trigger on where pcfControlCount > 0).
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered:
@manuelap-msft This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
Jenefer-Monroe
changed the title
[CoE Starter Kit - Feature]: Store PCF Control Count for PowerApps App table
[CoE Starter Kit - Feature]: Store App Compexity information (ex PCF Control Count) for PowerApps App table
Sep 8, 2023
Is your feature request related to a problem? Please describe.
The goal is to enable impact analysis for apps that use PCF components. The scenario is that an environment has PCF components enabled, and an admin may want to disable that - we then want to run an impact analysis to show which apps are using PCF components.
This information is available in new properties that have recently been added to the Get Apps as Admin output, in the appDocumentComplexity scope:
"appDocumentComplexity": {
"controlCount": 77,
"pcfControlCount": 9,
"uiComponentsCount": 7,
"totalRuleLengthOnStart": 2124,
"dataSourceCount": 11,
"totalRuleLengthHistogram": [
826,
560,
473,
36,
5,
2,
0,
0,
0,
0,
0,
0
],
"blocksOnStart": false,
"namedFormulasCount": 0,
"startScreenUsed": false
}
Describe the solution you'd like
Either if pcfControlCount > 0: store a true/false in a new field of usesPCFControls
OR (probably better option)
If we think we will use the appDocumentComplexity attributes for other purposes, such as showcasing complexity of an app (which could be relevant reporting), we could store pcfControlCount as a number (and then the reporting would trigger on where pcfControlCount > 0).
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: