Power Automate – Page 11 – Nishant Rana's Weblog

Using Force Sync User to sync PowerApp / CRM users – Power Platform / Dynamics 365

Recently in one of our trial environments, some of the users were not showing up in the Enabled Users view in Dynamics 365, although the users were having appropriate licenses assigned to them. (was more than 24 hours)

In such a scenario we can use Force Sync user action of Power Platform Management Connector.

https://docs.microsoft.com/en-us/connectors/powerplatformforadmins/

For Force Sync users, we will be passing the object id of the user and selecting the appropriate environment.

Run the flow manually.

It asks for the Object Id of user.

Inside Azure Portal >> Azure Active Directory >> Users, get the Object Id of the user

Currently, we have below 3 users in CRM

Let us run the flow.

Wait for the flow to complete.

After successful execution of the flow, back in CRM, we can see user 5 added to the list of enabled users.

In case we are using a security group for the environment we can make use of the below Power Automate Template, it takes the security group’s object id as input and loops through each of the members and applies Force Sync user action.

We can also make use of PowerShell cmdlets to achieve the same

https://nishantrana.me/2021/01/20/force-sync-users-from-azure-ad-to-dynamics-crm/

Force Sync Azure Active Directory Group members to specified CDS instance

Hope it helps..

Advertisements

Fixed – BadGateway. The request failed. Error code: ‘502’. Error Message: ‘BadGateway’ in PowerAutomate – Start and wait for an approval

Recently we were getting the below error for one of our Flows.

BadGateway. The request failed. Error code: ‘502’. Error Message: ‘BadGateway’.

Everything seemed right.

Finally, found (thanks to the forum) that the fix was to update the Approvals Administrator security role.

Provide – Read Access to System Job inside Customization tab.

Before –

After –

This time our flow worked smoothly.

Hope it helps..

Advertisements

Assign approvals to any user in the Tenant – Power Automate

We recently implemented Approvals, and we required that any user in the tenant should be able to provide approval.

For one of the users, we got the below error while testing the flow.

UserNotMemberOfCdsSecurityGroup

This was because we were using the Security Group to control access to Dataverse Environment.

So adding the user to the Security Group fixed the issue for us.

The user had the required CRM /Dataverse license.

Advertisements

Fixed – ‘InvalidApprovalCreateRequestAssignedToNoValidUsers’. Error Message: ‘Required field ‘assignedTo’ contained no valid users in the organization’.

We would get the below error while using Approvals in Power Automate

“BadRequest. The request failed. Error code: ‘InvalidApprovalCreateRequestAssignedToNoValidUsers’. Error Message: ‘Required field ‘assignedTo’ contained no valid users in the organization'”

This error occurs if we are trying to send the approval to the user which doesn’t exist in the organization or to the external users.

We recently got this error, and interestingly in our case, the user was showing up in the members in the Security Group inside Azure Admin Portal and was also giving us the option to add the user in Assigned To in the Flow.

However the user was not there in the Address Book of the Outlook, that is when we realized that user does not exist in the tenant anymore.

The flow can also fail if Assigned to a user’s personal account.

Here we have an option, to add the user as the Guest User.

Within Admin portal, navigate to Users >> Guest Users

Invite the user

The guest user needs to accept the invitation.

Back in our approval flow, we can now select the guest user added.

We can see the guest user getting the approval request

If we are using Security Group for the CRM Environment, than the user needs to be added to the Security Group also, else we will get the below exception – UserNotMemberofCdsSecurityGroup – The user cannot be created in Microsoft Dataverse because the account is not the member of the security group.

Fixed – Error code: ‘UserNotMemberOfCdsSecurityGroup’. Error Message: ‘The user ‘xyz’ cannot be created in Microsoft Dataverse because the account is not a member of group ‘abc’

In case we want to use approval with an external user(s) – without adding them as a guest user, we can use Send Email with Options Action instead of Power Automate Approvals.

https://debajmecrm.com/approvals-with-external-users-in-power-automate-without-consuming-power-automate-flow-license/

Hope it helps..

Advertisements

Fixed – Error code: ‘UserNotMemberOfCdsSecurityGroup’. Error Message: ‘The user ‘xyz’ cannot be created in Microsoft Dataverse because the account is not a member of group ‘abc’

We would get this error within Power Automate Approval Flow if we are using Security Group to control access to Dynamics 365 Environment and are sending Approval to a user who is not a member of that security group.

Below is the User within the Tenant but is not member of the My CRM Group Security Group associated with that Environment.

The Security Group – My CRM Group – assigned to Environment against which flow is created.

So to fix the issue, as the error message indicates, we need to add the user to the Security group.

After adding the user to the Security Group, the flow runs successfully

Also, the User (unlicensed in our case) gets added to CRM with Approvals
User security role as shown below.

Check other posts on Approvals –

Approvals – Power Automate & Dynamics 365

Hope it helps..

Advertisements

Fixed – Remote Server returned ‘550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP – using Send Email with Option in Power Automate

While trying to send an email using Send an email with options action in Power Automate to my email id from a trial account, got the access denied error message.

Check out the wonderful post on sending Approval Emails to external users

https://debajmecrm.com/approvals-with-external-users-in-power-automate-without-consuming-power-automate-flow-license/

The error message –