App for Outlook not working as expected

(0) Share

Report

Posted on by Steven O'Neill

575

Hi guys

Apologies for this (probably been asked before) but can anyone advise on what the Security Role settings should be for the App for Outlook to work correctly?

We're using V9 and I've done the following:

System Setting - MailApp Preview is set to Yes
Security Role - Business Management tab:
- Mailbox = Create/Read/Write/Append/Append To all set as Organisation
- Privacy Related Privileges = use Dynamics 365 App for Outlook is set to Organisation
Security Role - Customization tab:
- Entity = Read/Write set to Organisation;
- Field = Red/Write set to Organisation;
- Relationship = Read/Write set to Organisation;
- System Application Metadata = Read/Write set to Organisation;
- System Form = Read/Write set to Organisation;
- User Application Metadata = Read/Write set to User;
- View = Read/Write set to Organisation

I've then accessed the Getting Started with Microsoft Dynamics 365 App for Outlook page and Added the App to Outlook.

I've followed the guidance from here: https://technet.microsoft.com/en-us/library/dn946901.aspx.

The App is showing up in Office 365 and in Outlook but I'll focus on Office 365 here. When I access an email and click the D to open the App, the App will open but I will sometimes get a message in it saying: Error Loading Control (the outline of the app is there but no content).

If I apply the System Admin role to the user then the App works perfectly so I know there is a setting I'm missing somewhere here but I cannot locate any guidance on this other that the above. If I remove the System Admin role from the user the App continues to work for a while (I'm assuming session length here) but will ultimately return to the Error Loading Control message.

When I click on the Error Loading Control message I get this error:

Error while mapping state to props during ComponentDidMount for control: MscrmControls.Containers.DashboardControl

Any advice on where to look next? I know V9 App is in Preview but I don't think it's the Preview that's the issue here (as it works when the user is a System Admin) so I'm guessing it's a Security Role setting I need to tweak here.

Thanx for any advice.

Steven

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (0)

StaceyKCRM 80 on at

Like (0)

Report

Hi. Facing same issue. Did you ever get a resolution? Thanks for any insight.

Was this reply helpful? Yes No
Mr Ramzy GHRIBI 345 on at

Like (0)

Report

Hi,

the user who is accessing the Microsoft Dynamics CRM client for Outlook is in Restricted access mode ?

Was this reply helpful? Yes No
StaceyKCRM 80 on at

Like (0)

Report

Just to clarify...this is for the Dynamics 365 App for Outlook versus the Dynamics 365 for Outlook (full blown) client. As Steven mentions in his original post, if you give a User the Admin role in D365 the issue is no longer an issue. So it seems it’s definitely related to access/privileges, just not sure what the missing access/privileges are.

Was this reply helpful? Yes No
Suggested answer

Mr Ramzy GHRIBI 345 on at

Like (1)

Report

you can use another standard security role like sales director and test if it works properly. After that you can delete unwanted access/privelge and try every time until find the concerned access/privelege.

Was this reply helpful? Yes No
Steven O'Neill 575 on at

Like (0)

Report

Hi Savvy

Sorry to hear you're having the same issues. I've not had much chance to go back and review this issue but I also asked the question on the D365 Enterprise Edition forum here (community.dynamics.com/.../261546) and Financial IT Guy managed to fix his issue. I've not been able to try this fix as we are D365 Service Admins at this particular client (not Global Admins) and as such we need to jump through some hoops in order to get the internal IT guys to do something for us.

RAMZI does suggest going through all the other roles (makes sense) and it's something I'll try when I get a spare couple of hours!

If you do find a solution, I'd love to hear it though. When I figure it out then I'll also report it back here as well.

Cheers

Was this reply helpful? Yes No
Sergey Aksenov on at

Like (1)

Report

Hi Steven,

We're having exactly the same error with our CRM v9 Outlook app. Try to assign OOB role 'Salesperson' to a user and see if the error disappears. It worked for us, but I haven't found the exact authorization from this role yet.

Was this reply helpful? Yes No
KeithCachia 5 on at

Like (2)

Report

Hi, we are facing the same issue with our organization. We have noticed that the Outlook App only works with particular system roles, one of which is the 'salesperson' role. Since we were not using the role we have removed all permissions from the role and assigned it to the users that require access to the Outlook App.

Was this reply helpful? Yes No
Sergey Aksenov on at

Like (1)

Report

It's very likely that it's not about authorizations in the role but the role itself. I spent significant amount of time trying to figure out which authorization from Salesperson role works but had no success with that.

Was this reply helpful? Yes No
Steven O'Neill 575 on at

Like (0)

Report

Hi guys

Thanx for the update on this and we'll give this option a go here. Seems weird to me that this would fix it since standard guidance is to not use those roles at all but to copy and update. I'm guessing though that a copied version will act as the original one does and as such the issue may be fixed doing this.

We created new Security Roles from scratch and worked our way up with permissions so this could well be the problem...a blank non CRM based Security Role may have a permission issue in the background that we're not aware of.

I like the think from you guys here and we'll give this a try.

Thanx

Was this reply helpful? Yes No
Suggested answer

Thomas Rath 665 on at

Like (1)

Report

Hi Steve and all

I can confirm from almost 10 hours of investigation that there is a MAJOR bug in the App for Outlook! It only works with the standard security roles. It won't even work if you make a copy of on of the standard roles and use that without doing any changes to security. It seems that the app is somehow "hardcoded" to the standard roles. I'm very busy with projects at the moment and this bug did not do anything good for my available time. If anyone with some spare time would be so kind as to report the bug to MS I would be very grateful.

Was this reply helpful? Yes No