Recently while trying to delete some of the Queue (Advanced Queue) in our case, we were getting the below error.
You can’t delete this queue because it has items assigned to it. Assign these items to another user/team, or queue and try again.
We checked and there were no queue items assigned to that queue.
Eventually what worked was to Deactivate that Queue first and then we were able to delete it.
Hope it helps..
To enable quick sharing of the read-only link of the records to any users within the organization, log in to Power Platform Admin Center
Select the Environment > Settings > Privacy + Security
Switch On the Enable Sharing option
This option currently works on the Contact, Account, Opportunity, and Case table.
It enables the option of sending the link to the record with
apart from
Clicking on the Copy link opens the below model dialog box –
Clicking on People with existing access opens the below options –
Here we have selected “People in your organization with the link“
This enables any user (even if he has no CRM License or Dynamics 365/ Power Platform Role assigned) with the link to open the record as read-only.
This is how the record has opened for the user having no access to CRM but having the link to the record. (read-only)
Similarly, Email Link opens the Send Link dialog box, which allows us to select either a User(s) or Team(s) and define the content of the message as shown below
Clicking on Send opens the email in the default Mail Client associated
Here also we have the option to select either People in your organization with the link and Specific People
Get more details –
Hope it helps..
Recently one of the users, while accessing a few of the System User’s views, was getting the below error.
You do not have prvReadmsdyn_personasecurityrolemapping permission to access Persona Security Role Mapping records. Contact your Microsoft Dynamics 365 administrator for help.
There were a few System users’ views that were working fine.
The user had the Security Role = System Administrator, however, the Access Mode was set to Administrative.
Changing the Access Mode to Read-Write fixed the issue.
Hope it helps..
With recent security enhancements in Customer engagement apps, the maximum user session timeout of 24 hours is removed.
Now it uses the Azure AD Session Policy to manage user session timeout, which by default has Azure AD refresh token expiration set as 90 days.
Refresh toke lifetime and expiration – https://docs.microsoft.com/en-us/azure/active-directory/develop/refresh-tokens#refresh-token-lifetime
Use Configuring sign-in frequency in Conditional Access to define the periods before a user is required to sign-in again – https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
Earlier the default session timeout used to be 24 hours with 20 minutes for warning the user – https://nishantrana.me/2017/11/17/configure-session-timeout-and-inactivity-timeout-dynamics-365/
However, we can still override the default Azure AD Session policy, by setting the session timeout and/or inactivity timeout for the individual environment.
To set the same navigate to –
Environments > [Environment] > Settings > Privacy + Security in Power Platform Admin Center.
Specify appropriate values and save the changes.
Get all the details here –
Hope it helps..
Suppose we want to Test & Enable Mailbox of the below user programmatically.
We can see the below notification for the disabled mailbox.
This mailbox is disabled for email processing. For more information, see the alerts.
Below is the sample code –
On running the code, we can see the notification removed and the mailbox for the user enabled successfully.
C# Code –
CrmServiceClient svc = new CrmServiceClient(ConnectionString);
if (svc.IsReady)
{
var mailBox = new Entity("mailbox", new Guid("C88A539A-F493-EC11-B400-000D3A4F37D3"));
// testemailconfigurationscheduled = Indicates if the email configuration test has been scheduled for a mailbox record
mailBox.Attributes["testemailconfigurationscheduled"] = true;
svc.Update(mailBox);
Hope it helps..
Suppose we want to Approve the Email for the mailbox of the user(s) programmatically.
We’d see the below notification for the user whose mailbox is not yet approved.
Email won’t be processed for this mailbox until the email address of the mailbox is approved by an Office 365 Global Administrator or by an Exchange Administrator. For more information, contact your system administrator.
Below is the sample code –
On running the code, we can see the notification for the email address approval removed or the mailbox approved for the user.
C# Code –
CrmServiceClient svc = new CrmServiceClient(ConnectionString);
if (svc.IsReady)
{
var systemUser = new Entity("systemuser", new Guid("C48A539A-F493-EC11-B400-000D3A4F37D3"));
// emailrouteraccessapproval - status of the primary email address
//0 = Empty, 1 = Approved, 2 = Pending Approval, 3 = Rejected
systemUser.Attributes["emailrouteraccessapproval"] = new OptionSetValue(1);
svc.Update(systemUser)
The code should run under the context of the user who has either Global Admin or Exchange Admin role.
Hope it helps..
Nishant Rana's Weblog 