Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
CRM 2011 and SharePoint 2010.
The CRM List Component is activated and being used to serve up documents for Accounts. When you click on 'Documents', the iframe sits loading for about 7-15 seconds. CRM does not seem slow otherwise, and the SharePoint document library loads instantly if you browse to it directly.
What are some common causes of an issue like this? Any advice on where to start with troubleshooting?
Are you using the correct supported version of the list component?
If you trace using something like Fiddler, do you see any authentication issues or anything weird?
We too seem to have this issue as well and its usually been about 13 seconds for SharePoint to load in the iFrame within the CRM record. Recently in the last few days its now more like 20 seconds wait which is now quite painfull.
Does anyone know what to check or if this speed can be improved.
Our CRM servers are externally hosted at Rackspace and our internet connection in the office is usually about 15 to 20 Mbps. Connection to our CRM servers is fast when doing other activities. Acccess directly to sharepoint on Office 365 is also fine.
Why is CRM taking so long top load via the CRM list component?
Is there any update on this issue? We have the same issue using CRM 2011 and SharePoint online. It takes about 18 sec to load documents even if the doc lib is empty.
Posting this here as well. Microsoft says this is by design and will not be fixed. Do not waste your time troubleshooting this -- you cannot fix it. We spent over 100 hours on it, much of it with their support engineer.
Thanks for the advice Adam, we moved on from this now, and are looking at other Document management solutions.
Business Applications communities