Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have a question regarding CRM sharepoint integration. We use an iFrame to load sharepoint in CRM, but loading the iFrame lately takes more than 20 seconds. We have a single sign-on and the latest list components installed.
Does someone know what caused the loading problem?
Thanks in advance.
have there been any changes on your internal network? e.g. new virusscanners, new firewall rules.
If you ping the SharePoint online url, what are the response times?
Thanks for your reply.
There are no significant changes on our internal network.
If we access sharepoint directly from the site, it loads instantly. Also CRM is loading instantly.
Our admin tried increasing the resources on the server, but that didn't show any difference either.
Each component alone functions without any problems, but integrating crm and sharepoint gives issues.
having exactly the same issue here ! It takes ages to load the iframe - direct access to Sharepoint online through URL is fast.
Very much interested in a solution !
Could this just be from your SharePoint server "waking up"? Is the delay only on the initial load, or is there a long delay each time you load the iFrame?
It's for sure not "waking up" as a direct call by URL (see below locationUrl) to the corresponding site on the Sharepoint is rather quick. It is the call to the CRM list component (I guess) which takes ages every time it's called.
The call looks like this:
Any suggestions appreciated !
Do you have other solutions installed in the same SharePoint site collection? I've run into issues where SharePoint solutions conflict with the CRM list component.
I now set up a separate "clean" site collection to connect to CRM.
The other thing you should verify, is that both your CRM site and your SharePoint site are recognized as "Local Intranet" sites in your browser.
we have nothing else installed, just use the SP online as storage for our CRM on-premise. How can I make the browser believe that both servers are in the local intranet ? Haven't found anything explaining that ...
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.
Intranet sites can be managed by group policy. But if you're not doing that, you can set your local intranet sites up in IE, by going to Internet Options -> Local Intranet -> Sites.
Unfortunately I could not solve the issue with setting up the local intranet sites. It seems to me that this clearly comes from the crmlistcomponent solution - as the call to CrmGridActionsPage.aspx takes ages to return.
That problem is likely caused by the list component that is fetching all the data from SharePoint before it filters the records that are useful to you. There is nothing that you can do about it (or you have to use the serverside integration)
Do you have other solutions installed in your SharePoint environment that could be conflicting with the CRM solution?
This is the only other thing I can think of that would be giving you your long load times.
Unfortunately not, the crmlistcomponent solution is the only one we use as SharePoint in our case is only used to be storage for crm :(
This is a known issue for Microsoft, and their support person, after weeks of troubleshooting, said it will not be fixed. They said it is by design. I would not waste your time trying to fix it, as we spent well over a hundred hours total, only to have the end result be "that's the way it will work from now on."
Oh perfect! That's so typical for Microsoft !
Thanks anyway for letting us know!
Business Applications communities