we've been running to problems lately when our CRM 2011 automatically updates to the latest rollup (17 I think) coming from rollup 5. So what we've been doing now to resolve the problem is to uninstall the rollup since we're perfectly fine without the Rollup anyway. The problem is, after uninstalling the updates it just automatically updates itself again after some random time.
So the question is, is there a way to prevent CRM 2011 from automatically updating the Rollup? Any help is appreciated.
Thank you!
Update Rollup for Dynamics CRM can be applied to the Server or to the Client Outlook.
In your case you are referring to the Client Outlook, if the rollup is automatically installed you need to change the settings inside Windows Update, because the Update Rollup are also released using that channel.
Related
I'm working in MS Dynamics CRM 2015 on-premise and when files are downloaded from dynamics, the file gets downloaded but that name is getting enclosed with quotes (' '). Ex:'gs1630528410565.pdf'.
This behavior exist only in chrome and works perfectly fine in Firefox and Edge.
This is something to do with the issue introduced in particular chrome version.
As a workaround, use Edge or Firefox. Always you can rename the downloaded file, in case of chrome only work environment.
Read more
This is an ongoing issue with crm 2016 and crm 2016 onprem.
We are using crm 2016 and we face the same issue.
Below is the article mentioning same.
Till now we have to deal with this annoying issue.
Microsoft had same online as well but they fixed it online as they do not prioritize Onprem anymore
By the way do you use chrome as incognito mode?
https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/310058/mscrm-2015---downloaded-file-names-are-enclosed-with
We're developing and Outlook web add-in that needs requirement set 1.4, which is supported by both Outlook 2016 CTR and MSI.
We have Outlook 2016 MSI 64-bit installed on 2 different machines. Machine A has Outlook installed long ago and it has windows auto update turned on. Machine B has just had Outlook installed today without any update.
When we tested the add-in on both machine, it's loaded into Outlook of A, but not B. We figured out that Outlook on A is the latest version but Outlook on B is not, so we tried to trigger Windows update on B manually, but it cannot find any update for Outlook. We then tried to download and install the latest update for Outlook from this site, but the result is not as expected:
OUTLOOK.EXE is updated to 16.0.4732.1000, which is the same with
machine A
Outlook > File > Office Account > About Outlook still shows:
16.0.4266.1001, which is different from machine A: 16.0.4639.1000
Requirement Set is updated to 1.3, not 1.4 (we used F12Chooser to
check)
Is there any wrong with our update process? How can we have Outlook on B fully updated just like on machine A?
We recommend getting updates through Microsoft Update since it will update all of the right files.
In your specific case, for Outlook 2016, try also installing this update, which is needed for requirement set 1.4.
We recently upgraded to Dynamics 365 from CRM Online 2016. As a result all our CRM Organizations and Regions are no longer appearing in the Unified Service Desk CRM Organization selection window. Kindly advise on how to restore.
It Seems that you were force updated, acoording to the Update Policy the minor version supported is n-2 (8.1 in the current scenario) if you want to go back to 8.0 it won't be possible cause isn't supported any more, if you want to go back to any of the supported previous versions could restore one of the snapshot of the database that if aven't pass more than 3 days, in that case you could create a customer support ticket and ask for an older backup
Hope it helps
I have a Production instance on CRM 2015 Update 1. Once I update to Dynamics CRM 2016 and get a Sandbox instance after that, will the new Sandbox instance after I update to 2016 be the new 2016 version or the Dynamics CRM 2015 Update 1 version?
I'm pretty sure that new Sandbox will be CRM 2016 based.
I'm assuming you already have a sandbox 2015 update 1 instance, but your question sounds like you'll get a sandbox after you upgrade. Our normal upgrade process is to upgrade the sandbox first, perform some system tests, and then send the "All Clear" message to have the production instance updated. You'll want to follow these steps as well to ensure that an update doesn't break any of your customizations.
I am doing some research on building integrations for Microsoft Dynamics CRM Online. The integration I am building will be for Dynamics CRM Online 2013, but I am curious if the 2013 version shares an API with the 2011 version.
Does anyone know if an integration built for Dynamics CRM Online 2013 will be backwards compatible with Dynamics CRM Online 2011?
Any insight here would be appreciated.
Also, if anyone has good resources for working with these API's using Ruby that would be awesome...
Thanks!
I wrote some integration for CRM 2011 Online (C# and PHP/SOAP) and I can happily say both still work.
Any integration written with CRM4 in mind would need some modifications I believe (this may just be changing the endpoints) but 2011 and 2013 seem to work ok together.
If you are wanting to connect using a non .Net language be careful as it can be significantly more painful then creating a wrapper for the web service then talking to that from Ruby.
To connect with a non .Net language you need to use SOAP. I have put some posts here (PHP code but it should be easy enough to convert)
http://crmtroubleshoot.blogspot.com.au/2013/07/dynamics-crm-2011-php-and-soap-using.html
I currently don't have it working with Active Directory authentication though!
Everything that I've read about the API changes from 2011 to 2013 has boiled down to the removal of the CRM 4 aspx endpoint. Besides that, most of the changes to CRM are front end.
I read somewhere that a solution made in 2013 can't be exported in 2011. So I don't think will be retro-compatible.
Chapter-
Introduction to solutions
here it is from the SDK:
Version compatibility
Solutions exported from an older version can be imported into newer versions. Solutions exported from newer versions cannot be imported into older versions. This includes major and minor version differences.
Solutions exported from a Microsoft Dynamics CRM 2011 environment or a Microsoft Dynamics CRM Online organization prior to the Fall '13 Service Update can be imported into organizations using the initial release of Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online Fall '13 Service Update. However as updates are applied and include new features or metadata definitions, these new features or definitions cannot be included in a solution that is installed on an organization that is not current with the definition that the solution was exported from.