Microsoft Certified: Power Automate RPA Developer Associate PL-500 Reddit Questions

No, Yes, No

According to the scenario, you are unable to save ProdManager because it uses a connection reference that is missing from ProductionMonitor. To resolve this issue, you can use the Connection References page to add the missing embedded connection references to ProductionMonitor. This way, you can ensure that both cloud flows use the same connection reference and avoid errors.

Adding the current user as a co-owner of ProductionMonitor will not resolve the issue, because co-owners cannot modify the connections or connection references used by a cloud flow. Changing the value of the Run only users setting for ProductionMonitor will also not resolve the issue, because this setting only affects how run-only users can access connections when they run a cloud flow manually.

According to the scenario, you want to run the desktop flow actions in unattended mode when the cloud flow is triggered by a schedule, and in attended mode when the cloud flow is triggered manually. To achieve this, you can create an environment variable that stores the run mode value (attended or unattended) and use it as an input for each desktop flow action. This way, you can change the run mode value dynamically without having to manually update each action.

According to the scenario, you want to package all your automations into a single solution that can be easily deployed across environments. To do this, you need to add existing components to the solution, such as cloud flows, desktop flows, connections, and custom connectors. This way, you can bundle all your related resources into one package and export or import it as needed.

To implement security to resolve the invoice data issue, you need to perform three actions:

In Microsoft Power Platform admin center, navigate to the Security roles section. This is where you can manage the security roles for your environment and assign them to users or teams.

Select the Finance role, select Custom Entities and navigate to the table. This is where you can configure the access level for each entity in your environment based on your security role.

Clear the Create and Delete permissions. Set the Read permission and Write permission values to Business unit. This will restrict users with this role from creating or deleting records in this table, but allow them to read or write records within their business unit.