Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Dynamics 365 App for Outlook is installed and working, however, performance, when set regarding, is very poor. We believe this is because of the App searching ALL entities in our configuration, of which, we only require 7 or 8 to be searchable in the Outlook APP
1 - We have updated the 'Configure Relevance Search' to only show the required entities
2 - We have updated some of the entities as a test to remove the enabled 'Reading pane in Dynamics 365 for Outlook'
At present this has made no difference.
Does anybody know how to control the entities 'set regarding' searches?
Hi - we're having the same problem... this is a deal breaker for us!
Unfortunately, once an entity has the Activities enabled, it cannot be undone:
What I would like to suggest then is to create a new security role and limit/restrict the entities on the list that are not necessary for the Set Regarding functionality. This should help you in testing if the Set Regarding is slow due to the number of entities shown in the list.
If you wish to enable this functionality of displaying only the entities you require on the Set Regarding list, please cast your vote on the following page.
Thanks for responding Barry.
What we have found at security role level is that the entities that we don't require in the 'Set Regarding' of the Outlook App are configured to 'None selected'. All of the entities are as you say, "configured at entity level for 'Activities'" that can't be updated.
Is there a way that you know of using ODBC or other where you can update the database directly to the entity field that stores the Activity = True checkbox ?
We're struggling to think of another way around this other than start deleting some of these entities altogether if they're not being used
Unfortunately there is no ODBC solution (supported) to this, once the entity has been created, this option is greyed out, whether or not the option was ticked or not.
We have the same issue and my thoughts is that it's taking to much data in consideration when syncing and it is to much for Outlook. As in OWA app works much faster and don't hang up.
Have you managed to solve this issue? Or someone knows how to change default search criteria from All to Account or Contact?
We found this issue as soon as we went to Version 9. After many hours of trying to work out how to change the settings we logged a case with Microsoft and was told that this is by design. Our Outlook App constantly crashes when trying to Set Regarding as it is searching across many many entities in our CRM. We have Portals, Project Service and ClickDimensions installed, so have many activity enabled entities.
Unfortunately not, your idea of setting the default search from ALL to a another would be a good feature too. If you find out anything please post
V9 has quite a bit to answer for it must be said. We're having the same issues as you, so much so, we can't deploy the APP to the workforce as it just isn't performing. This is meant to be a 'time saver' feature, unfortunately, the UX/Design team at MS need to revisit this as a matter of urgency in my opinion.
There must be an OBDC connector that enables you to get to the entity information table so that you can update the 'activities' field to false, thus removing from Relevance search. Here's hoping !
One last attempt at this: Under the Outlook & Mobile section, is Enable for Mobile ticked?
Try removing this option from a few of the entities and see if it removed itself from the list of available entities.
Again, if this doesn't work, please cast your vote on the following page: https://experience.dynamics.com/ideas/idea/?ideaid=605f895c-131a-e611-80e2-c4346badc228
If Microsoft is not aware of how important this functionality is, they will not look into it.
We had to tell our team to track the emails w/o using the set regarding. We created a recent email view for them so that they could go into CRM and set regarding from there. Hopefully MS will fix this soon, as that is an atrocious work around.
Unfortunately this didn't make any difference, thanks for suggestion
Thanks for all the suggestions Barry, much appreciated. We have logged this with Microsoft to investigate and provide, I hope, a short and long term solution to this. I will post again as soon as I have something to report from MS
at the moment we are using a workaround to track records from Outlook to Dynamics 365 until bug will be fixed by MS.
Please proceed following steps to be able to track e-mails in Outlook.
1st step is to Clean browsing history in Internet Explorer
(as Outlook app is connecting to CRM over IE in the background)
Clearing the cache of Internet Explorer 11:
2nd instructions how to track Appointments and e-mails (3 steps)
1. Use Global search to set regarding
2. Add account name in search bar and select record which you were searching
3. Press on a link button which will do set regarding.
Thanks for recommendation. What we have found is that when searching via set regarding, the performance is so poor we often have APP restart errors as it takes too long to load/find the required 'record'. More often than not its a custom entity record we're searching.
If the performance of the search was satisfactory we'd not have an issue with it looking at all entities where activities is enabled in the configuration of the entity.
Try to search over Global search it works much faster! And app doesn't brake up.
If you are in the App Editor, open the Site Map Designer (by clicking on SiteMap in the App Editor). Make any changes required by adding entities, areas and groups, then Save. You will see in the top right corner that it now says *Draft. Click Publish to make it live. Now Save and Close the Site Map Designer to return to the App Designer.
In the App Designer, in the top right corner, make sure to Save, then Publish the App. You can then Save and Close the App Designer.
The next time you open the App for Outlook, it will use the new configuration.
Yes it looks like Microsoft have a fix for this in CRM version 184.108.40.2069 due for release 6th July 2018.
The fix is that only the entities configured in the relevance search configuration in the default solutions/entities will be displayed and searchable via the Outlook APP
Perfect that worked. ! - Thanks Simon (only needed tweak and then publish App Designer stage by adding custom entities)
So for all to benefit - you need to be on at least 220.127.116.113
1 - Configure your relevance search in default solution
2 - Add custom entities and/or add required standard entities, save and publish top right of screen
3 - Re launch Outlook
If you are in CRM 9.0 than you can filter entities which show in set regarding through "App Designer". Its documented :
Business Applications communities