Microsoft retired the Power Platform App Maker Associate credential associated with PL-100 in 2024. The historical certification page is not a current exam registration route. Makers still need to turn business requirements into usable forms, reliable data relationships and permission-aware workflows. This article explains how to approach that work without suggesting that the old PL-100 exam can still be booked.
Define the business process before opening a designer
Identify who starts an action, what information must be captured and how the organization knows it is complete. A request-approval app needs the requester’s identity, an approver, a decision, timestamps and a defensible audit trail. Creating screens first often hides the missing states: withdrawn, delegated, overdue or rejected.
Write a small state-transition table. For each step, specify who may perform it and what data changes. The model should prevent approvals by unauthorized accounts even if they can reach the user interface.
Choose the data source based on relationships
Dataverse offers relational modeling, access controls and platform integrations; simpler lists or other sources may suffice for narrower workflows. Determine whether records share owners, require many-to-many relationships, need transactions or have data residency constraints. A collection of uncontrolled spreadsheet copies rarely supports a reliable shared business process.
Model keys and reference fields carefully. Test duplicate submissions and missing related records. Decide what to do when an upstream system corrects a customer name after an approval is already recorded.
Make app permissions part of the design
An equipment-loan app can expose the weaknesses of a form-first approach. Employees submit a request; an approver checks availability; the storekeeper issues an item; a return closes the lifecycle. If the app has only “Requested” and “Approved” states, it cannot reliably show items that were issued, returned damaged or never collected. Define each state, the actor authorized to change it and the associated evidence. Model equipment identity separately from requests so the same item cannot be issued to two employees simultaneously. Then test competing requests and cancellation after approval. These details determine whether the app is useful for operations, irrespective of the former PL-100 exam structure.
A user being able to see an app does not prove they should read every record in its data source. Validate roles and table/row permissions at the underlying platform boundary. Masking a field in the visual layer is not a security rule. Administrative connections and automation identities also need scopes appropriate to their duties.
Test one requester, one approver and one unrelated employee. Attempt to retrieve or change the same record through supported interfaces and verify that each request is handled according to policy.
Build workflows that handle retries and exceptions
Power Automate can notify an approver, record a result or update another service. But workflow execution may be retried after timeouts; duplicate deliveries should not create multiple approvals or accounting entries. Specify an idempotent identifier for the business action and retain an exception queue for unrecoverable failures.
An external API may be unavailable or return invalid data. The app must not tell the requester that an operation succeeded before the relevant system confirmed it.
Design forms for reliable data entry
A maker should also be able to explain when a low-code tool is the wrong abstraction. Complex transactional operations, highly constrained security requirements or specialized high-volume processing may call for a service designed for those constraints, with the Power Apps interface acting as a client. Choose based on failure modes, ownership and ability to test. An app that hides all business logic in dozens of undocumented formulas can become difficult to maintain even though it was quick to prototype. Move shared validation or sensitive operations to a clearly owned boundary and preserve traceable error messages. This decision is part of real application design rather than the former PL-100 exam’s feature checklist.
Required fields, validation, accessible labels and mobile behavior can prevent operational errors. Avoid presenting ten optional fields when only three determine the next decision. Use consistent error messages that tell the user what can be fixed, while not revealing privileged records or internal identifiers.
Test long values, unusual punctuation, missing attachments and simultaneous submissions. A successful standard happy-path demo is not sufficient acceptance evidence.
Measure app adoption and safe change delivery
A second test focuses on access and history. Suppose an employee moves departments while an equipment-loan request remains open. The app needs a clear rule for who may see past approvals, whether ownership transfers and which fields are immutable audit evidence. Power Automate retries should not issue the equipment twice when a response is delayed. Verify the data layer’s role enforcement rather than relying on a hidden button. Finally, rehearse an app-version rollback and check that existing records remain interpretable. That exercise covers business rules, Dataverse modeling, automation and governance as one integrated design problem rather than separate marketing features.
Track completion time, reopened requests, validation failures and manual workarounds, not simply sign-in counts. Introduce a versioned app change to a pilot group, review its effect on existing records and define how to revert a broken formula or permission rule. Document connector ownership, licensed dependencies and platform limits.
For career development, choose current Microsoft training based on whether your role is app maker, administrator, functional consultant or developer. The old PL-100 blueprint is a historical reference only.
A well-built business app makes responsibilities and data rules explicit. Those design and testing habits remain relevant even after the App Maker examination retires.