Microsoft Certified: Power Platform App Maker Associate PL-100 Release Date

Scenario: When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version.

Power Apps has added components to the rule set that encourages best practices in the Power Apps Checker. You can check your canvas apps and flows that are included in solutions and then review all issues in a single, consolidated report.

Box 1: 1.0.0.0

When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version.

A solution’s version has the following format: major.minor.build.revision. An update must have a higher major, minor, build or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more signficant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0.

Box 2: 20.11.1.1

Scenario:

• You must use the following version control numbering scheme:

- Major: The last two digits of the year the app is packaged

- Minor: Two digits that represent the month when the app is packaged

- Build: A number that is incremented to represent significant changes to the app

- Revision: The incremented revision for a package

New versions of the application must completely replace previous versions of the app.

Box 1: Fill

Scenario: You must display a visual indicator in the app so that sales representatives know whether the app is offline before submitting reports.

Fill – The background color of a control.

Graphical user interface, text, application Description automatically generated

Box 1: AccessibleLabel

Scenario: Before deploying the app to production, you must ensure that the app conforms to Microsoft accessibility and performance guidelines.

User2 is visually impaired and cannot see images.

AccessibleLabel is a label for screen readers.

An empty value for Image, Icon, and Shape controls will hide the controls from screen reader users.

Box 2: TabIndex

User3 is unable to use a mouse.

TabIndex determines if the control participates in keyboard navigation.

Keyboard navigation is an important aspect of any app. For many, the keyboard is more efficient than using touch or a mouse. The navigation order should:

Mirror what is seen visually.

Only have a tab stop at controls that are interactive.

Follow either an intuitive across and then down "Z" order or a down and then across "reverse-N" order.