Microsoft Certified: Power Platform Developer Associate PL-400 Release Date

Box 1: Environment Maker

UserA must be able to create and publish Power Apps apps.

The Environment Maker role can create resources within an environment including apps, connections, custom connectors, gateways, and flows using Power Automate.

Box 2: System Administrator

UserB must be the owner of all the systems and be able to provide permissions and create all new environments.

The System Administrator has full permission to customize the system. Can view all data in the system.

Box 3: System Customizer

UserC must be able to create apps connected to the systems and update the security roles and entities.

The System Customizer has full permission to customize the system. Can only view rows for system tables that they create.

The difference between the System Administrator and System Customizer security roles is that a system administrator has read privileges on most rows in the system and can see everything. Assign the System Customizer role to someone who needs to perform customization tasks but shouldn’t see any data in the system tables.

Box 4: Common Data Service User

To stay consistent with our product rebranding effort, the security role Common Data Service User is being changed to Basic User.

The Basic User security role primarily contains Basic privileges for core entities where the user can write, update, and delete records that they created or owned.

Box 1: Custom self-service portal for both employers and job candidates

If you select an environment that contains customer engagement, you can create the following portals:

Customer self-service portal: A customer self-service portal enables customers to access self-service knowledge, support resources, view the progress of their cases, and provide feedback.

Partner portal: A partner portal allows every organization with resellers, distributors, suppliers, or partners to have real-time access to every stage of shared activities.

Employee self-service portal: An employee self-service portal creates an efficient and well-informed workforce by streamlining common tasks and empowering every employee with a definitive source of knowledge.

Box 2: Model-driven app with push notifications

Compared to canvas apps, model-driven apps in PowerApps are based on underlying data — specifically, the data stored in Common Data Service (CDS).

Box 3: Webform with target set to the job custom entity

Box 4: Configure a value for the Execute Workflow on Redeeming Contact option only.

Execute Workflow on Redeeming Contact: A workflow process to be executed when the invite is redeemed. The workflow will be passed the redeeming contact as the primary entity.

Box 5: Configure the value for the Assigned to Account option only.

Assign to Account: An account record to be associated as the redeeming contact's parent customer when the invite is redeemed.

The ClearCollect function deletes all the records from a collection.

Syntax: ClearCollect( Collection, Item, ... )

Collection – Required. The collection that you want to clear and then add data to.

Item(s) - Required. One or more records or tables to add to the data source.

Box 1: Yes

The Patch function in Power Apps modifies or creates one or more records in a data source, or merges records outside of a data source.

Use Patch with the Defaults function to create records.

Box 2: No

The return value of Patch is the record that you modified or created. If you created a record, the return value may include properties that the data source generated automatically. However, the return value doesn't provide a value for fields of a related table.

For example, you use Set(MyAccount, Patch(Accounts, First(Account), 'Account Name': "Example name"); and then MyAccount.'Primary Contact'.'Full Name'. You can't yield a full name in this case. Instead, to access the fields of a related table, use a separate lookup such as:

LookUp(Accounts, Account = MyAccount.Account).'Primary Contact'.'Full Name

Box 3: Yes

Box 4: Yes

Merge records outside of a data source.

Specify two or more records that you want to merge. Records are processed in the order from the beginning of the argument list to the end, with later property values overriding earlier ones.

Patch returns the merged record and doesn't modify its arguments or records in any data sources.