In late crm 4, email address resolution behavior was changed. In earlier versions, if you had an e-mail address on multiple records (account, contact, lead, user), it would only resolve to one of them. This behavior was changed so that if there are multiple records with the same address, when an e-mail comes in with that address as a recipient, CRM will resolve to all of the records with that address, creating multiple activity parties.
Some implementations have duplicate email addresses by design, and this multiple resolution can cause problems in some situations, such as confusing users when they see 10+ recipient activity parties for the same address, and can cause emails to get linked to the wrong records.
Please add additional system settings to make CRM work better in these scenarios. Additional options that would be good:
Ability to turn off email address resolution
Ability to turn off email address resolution to inactive records
Ability to select (control) record types for email address resolution
option for Track None for incoming mail
When we configure CRM Client for Outlook and track records in Outlook configured in CRM we see tracking icon which helps us to understand that the record is tracked in Dynamics 365 organization.
However when we configure CRM App for Outlook, we do not see tracking icon when we track records from Outlook desktop or Outlook Web App (OWA).
This makes the user difficult to understand if the email is already tracked in CRM and have to manually check the details on each record in outlook.
Can't believe nobody's posted this yet. I just searched for the word 'crash' and found only two references to Outlook, with only 1 vote each. Maybe this is unique to our environment so if anyone has a suggestion, I'm all ears. But I haven't found one yet so I'm posting here.
We're running a combination of Office 2007/2010 on Windows 7 SP1 x64 systems. The Outlook clients all worked fine, with or without the CRM 4 clients. Then after upgrading to CRM 2011/RU5, we've had nothing but complaints from users who have their Outlook sessions crash at various times throughout the day, without any apparent pattern of usage to begin to isolate the problems.
All we get in the event logs are Outlook app crash errors, event ID 1000 - nothing specific. As soon as we remove the CRM client, no more crashing.
It's pretty important that this work without crashing the client all day - it's deterring users from wanting to use the product.
The builtin html editor used to edit emails and email templates is very restrictive and troublesome when using copy/paste.
- Font end up different for pasted text
- Formatting options are minimal (eg. no tables, etc)
The current workaround that most people use is to copy the email text from the template into notepad/word, edit it there and paste it back. The Problem then is that formatting is lost altogether along with hyperlinks (if done in Notepad to avoid font issues).
Please consider including an already accepted standard editor like Telerik's RadEditor or CKEditor to provide users with a more workable emailing method.
Users that track the majority of their email using the App for Outlook find it very time consuming and frustrating to keep having to click the "Dynamics 365" button in the Outlook ribbon to re-open the App for Outlook after selecting each email.
If there was an option to "pin" the app so it stays open between emails this would much improve the UX of this feature.
We have an issue where when we add a room to an appointment and sync it with CRM, the room gets removed. It is getting changed from a resource to a required attendee.
We have employees that are constantly late or miss meetings because they do not know where to go.
I opened a case with Microsoft and they said that this was working as designed.
Every time an item (email/appointment etc) is tracked within Outlook using the Outlook client for CRM 2015 a dialog with a progress bar pops up saying, "Contacting CRM", followed by "Wrapping up". This takes away focus from the Outlook window (and anything else you're doing) and nothing can be done until the messages go away. If you're tracking large emails or have a lot to track this can take some time. It has only been introduced with the 2015 version of the client and it needs to be taken away. The user should not be informed that a background track is happening. Why do they need to know? More to the point, why should it stop them doing anything else while it does it's thing.
Add Subfolders to Server-based SharePoint Integration for Microsoft Dynamics CRM Online and SharePoint Online
As explained here: http://msdn.microsoft.com/en-in/library/gg334768.aspx
CRM online no longer requires you to use the list component in SharePoint for document integration. You can upgrade to this new feature called Server Side integration. The new server side integration no longer allows SharePoint folders/subfolders to be listed in CRM under Documents. Instead it only displays documents. Folders used to be available/viewable in the CRM document location when the list component was being used. Customers who upgrade to the new server side sync lose this functionality. This is a huge pain point for people who are accustomed to organizing their documents and having them displayed in CRM. Please re-add the ablitiy to display folders sub folders within CRM through the server side sharepoint integration mechanism as it was before with the list component. Or, please allow CRM customers who have upgraded to server side sharepoint integration to revert back to be able to use the list component.
Currently e-mail messages sent to distribution lists or aliases are discarded by the E-mail Router with the warning "NoRecipientMatch" because the list or alias address is not known to CRM. We suggest implementing an additional setting on the Mailbox entity to specify whether the E-mail Router should skip/omit the recipient address check for this User/Queue and instead just copy the message into CRM. This would enable the E-mail Router to import all incoming messages to CRM regardless of the e-mail address(es) in the message (note that this also includes BCC messages!). This solution obviously does not work when using a Forward Mailbox with the E-mail Router, but it does enable more comprehensive incoming e-mail handling for critical mailboxes that are directly monitored by the E-mail Router.
For reference, there already exists an earlier, similar suggestion:
E-mail router should be able to handle E-mails sent via distribution lists