CRM 2013: How to disable autosave so my plug-in code won’t be effected


With Microsoft Dynamics CRM 2013, the feature of auto save has been introduced. This feature is really long overdue, and its a feature we often overlook each day. For example, if your typing an email response on your cellphone, and the phone rings, you answer it and go back to work, right? When you returned, your email was right where you left off!

This is the same concept for CRM 2013, and not forcing users to constantly press save and close. As you work on the system the data is periodically saved as indicated by the icon on the button right of the new UI.

savediconcrm2013

saveiconcrm2013

 

 

 

As you can see above, the first ICON of the disc shows everything is saved. As you begin to work the icon changes letting you know you have unsaved changes to the page. If you wait for about 5 seconds the auto save feature will kick in and automatically save those changes for you!

While Microsoft CRM 2013 is certainly thinking ahead of design and form, many CRM 2011 plugins were designed to fire after a user saves a record. This save is captured and the plugin is fired, in this case, over and over again each time auto save kicks in.

Thankfully, Microsoft gave us an option to turn off auto-save for this release to help upgrading customers
whom may not have updated their plugin/sdk code as of yet. Please note, this feature will not be available in future releases, and your new designs should use the SDK Method that works with auto save.

For now, under system settings, you can click the button to disable to the auto save feature and save your upgrade and plugins! This will save you for now, but make sure to look to the future when considering to disable this useful option! Enjoy!

autosave2013

 

 

 

 

 

 

The CRM 2013 SDK also will provide insight into new methods available to watch the state of change.autosaveSDK

 


Using Microsoft Dynamics CRM 2011 and Internet Explorer 10


Here’s one to make note of. With the introduction of Windows 8, IE 10 is quickly becoming the standard for desktop browsers, with IE 11 right around the corner with Windows 8.1 Release this fall.

As of Update Rollup 10, Microsoft Dynamics CRM 2011 is compatible with Internet Explorer 10 for the desktop in Compatibility Mode. For Update Rollup 12, or the December 2012 Service Update, Microsoft Dynamics CRM 2011 is compatible with Internet Explorer 10 for the desktop without Compatibility Mode.

Please Note: In both of the above circumstances, Internet Explorer 10 support is limited to the desktop browser mode, and does not apply to the touch version of the browser.

We get a ton of support tickets in how do I setup my IE 10 to work best with CRM 2011. Here’s
what you need to accomplish:

To change the Compatibility Mode of Internet Explorer 10, follow the steps below:

1. Right-click the top toolbar within Internet Explorer 10

2. Select to mark Menu Bar

3. Point to Tools and click Compatibility View Settings

4. Here, mark the Display all websites in Compatibility View checkbox or enter the specific CRM URLs under Add this website and click Add

Known Issues
Known issues that may be encountered when using Microsoft Dynamics CRM 2011 with Update Rollup 10 in Internet Explorer 10 for the desktop in Compatibility Mode:
•The dropdown list doesn’t expand if there is only one item in it. For example:

1.Logon to the Microsoft Dynamics CRM web application
2.Click Service and click Service Calendar. Make sure the type is Resource
3.Click the drop down list View
4.Notice that the list items do not expand

http://support.microsoft.com/kb/2743941


CRM 2011 Outlook Client: Disable Mapi Caching not working after UR 14


CRM 2011 Dynamics Customers testing and deploying update Rollup 14, have noticed that performance issues resolved in Outlook Client have returned. The registry key for Disable Mapi Caching appears to be no longer be working (reintroduces poor outlook client performance).

Microsoft Support has confirmed that the setting has now been moved to the OrgDbOrgSetting as follows:

DisableMapiCaching Boolean

AddressBookMaterializedViewsEnabled Boolean

It’s recommended to keep your older registry key in place as well to avoid any further issues should a future update switch back to the registry key method.

For information on the OrgDbOrgSetting Tool for Microsoft Dynamics CRM 2011

http://support.microsoft.com/kb/2691237

For more details on the disable Mapi caching for CRM 2011 Outlook client, please review the Microsoft KBs:

http://support.microsoft.com/kb/288894

http://support.microsoft.com/kb/2585157

 

 


Gearing up for Orion.. Are you ready to take the plunge?


The Microsoft CRM Product Team has been hard at work getting ready to deliver CRM “Orion” to the masses. We have heard we will receive the preview releases to begin testing very soon – (NDA-Safe :). We have also heard that Microsoft support was also training on the Orion Release. From Convergence 2013, there’s a lot of items we need to consider when getting ready Orion!

Remember, if you’re running CRM 3/4 you will still have to upgrade to CRM 2011 BEFORE moving to ORION.

Here’s my short list:

1. CRM namespace (jscript with crm.XXX) will no longer work and has been fully depreciated.)

2. Design Considerations for implementing the Process Flow UI – have you seen the process flow
UI available with (CRM Online code name Polaris)? If not, setup a trial or review my Convergence
debrief for screen shots. Sales users absolutely love the new Process Flow UI, great performance gains,
auto saves and one place instead of navigating to leads, accounts and contacts when working on an
opportunity. But consider how your business process can be revised in your existing CRM solution
to take advantage of this feature and the new form design. I expect that new features would only
be available to these new forms similar to the previous CRM Online Polaris release.

3. Consideration for running on SQL 2012 – CRM 2011 supports both 2008/2012 but for your new launch
consider migrating your servers to the latest releases.

4. Consideration for Windows Server 2012 – CRM 2011 supports both 2008/2012 but for your new launch
consider migrating your servers to the latest releases. ADFS 2.1 is also provided for Windows Server 2012,
but be currently not compatible with Online to OnPremise ADFS Federation if needed. (Use ADFS 2.0).

5. Remember to setup your test and development environments first! You will want to completely test this
rollout before deploying to your production servers. Also keep in mind that you need support your existing
CRM installation so a new development environment would be a good choice while you work thru testing Orion.

Stay tuned for more exciting announcements, screen shares and updates as we get closer!


Update Rollup 13 – Self Healing .MSP Patch Location CRM 2011 Install on Windows Server 2012


Installing CRM 2011 on Windows Server 2012 requires to use the Microsoft Self healing Process – manual patch that you download from the Windows Catalog. I searched all over and had a hard time finding it. Thanks to my good friend Corey Hanson at Microsoft for providing a direct link to the patch. The patch is listed on the KB article under manual installation, but its a bit unclear for those looking for the Self Healing Patch.

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=Setup%20Update%20CRM

Once you download the patch, add this to a directory on the CRM server. You will then run a command line install of CRM 2011 in order to have the installer use this patch. The CRM 2011 setup program will be updated upon release of Update Rollup 14, no longer requiring this manual patch for installing on Windows Server 2012. Instruction on how to create the configuration file and use the patch can be found here:
Example Sample Config.XML File – Save as XML – Do not save as TXT and rename.
 sampleconfig

Running from the command line:
commandline

Some more Gotchas:
Apparently, your must expand/unzip this file on a Windows 7 or Windows 8 machine, and then copy it over to the Windows 2012 Server. I kept getting messages that this patch will not work on this application and the serversetup.log file stated it was an invalid windows installer package.

2012installerror

 

Once I expanded (you can extract via right click too!) on my Windows 8 machine, and copied it over, everything worked like a charm.  This should save some people a few hours of scratching their heads..

Enjoy!


CRM 4 Support: End of the Line! Time to Upgrade Folks! or fall 2 versions behind!


Microsoft Dynamics CRM 4.0 On-Premise Support Lifecycle, will change effective April 9, 2013.

So what’s changing?
On April 9, 2013, Dynamics CRM 4.0 moves from the mainstream support phase to the extended support phase. What this really means is that customers who are currently running CRM 4.0 On-Premise and would like to continue to do so (without having to upgrade in 2013) will no longer receive the following non-mission-critical support items:
• Non-security hotfix support
• No-charge incident support
• Warranty claims
• Design changes and feature requests

Customers are not forced to upgrade to CRM 2011, but they should consider and understand what these changes mean to their organization and CRM deployment going forward.

To be clear, we do still support our Dynamics CRM 4.0 customers, but the parameters of that support change April 9, 2013.


CRM 2011 Update Rollup 12 has been released. Polaris is here!


Microsoft has officially released Microsoft Dynamics CRM 2011 Update Rollup 12, formerly known as Polaris.

https://community.dynamics.com/product/crm/crmnontechnical/b/crmconnection/archive/2013/01/29/announcing-the-availability-of-microsoft-dynamics-crm-2011-update-rollup-12.aspx

Download it here !

http://www.microsoft.com/en-us/download/details.aspx?id=36229

And let’s not forget our best practices!

http://msdynamicsworld.com/story/listen-voice-experience-decisions-will-help-or-hinder-microsoft-dynamics-crm-2011-upgrade

 


CRM 2011: Removing or Reinstalling ADFS Gotchas


ADFS can be very unforgiving if you need to uninstall or reconfigure. The following steps should steer you clear of any issues that you might run into. (ACL List issues are covered on my blog as well).

Step 1:
Uninstall ADFS using the control panel, remove program
NOTE:- ADFS will be shown as an installed update not a program. System will require a reboot.

Step 2:
Open IIS, find the ADFS Website, now delete the folders
Delete LS Folder
Delete ADFS Folder

Step 3:
View ADFS Application Pool
Note: You should see that there no applications now assigned to.
Delete ADFS Application Pool

Step 4:
Delete Program Files\ADFS installation path

Step 5:
IIS Restart

Now you’re ready to reinstall ADFS. Please make sure you download the latest ADFS 2.0 from the Microsoft Download Center, and don’t install/add the ADFS role from the Windows Server.