Today, when I launched Outlook I received what looked like a terrifying message that our CRM organization was disabled. One of the benefits of being a CRM MVP is access to the CRM Product Team. After posting this to our group I received a very prompt explanation.

It appears that due to the broad range of changes to the CRM metadatabase from SP1, the first time sync to CRM from Outlook can take substantially longer. The team added the notification to alert you that it would take more time that longer to sync with Outlook. In my case it took only about 5 minutes.

So don’t worry, this is all standard operating procedure. By the time you read this post, the message may have likely been edited, specifically the part where it says” your crm organization has been disabled’. They are going to tone that down.

Outlook CRM Add-n Sync Message

Outlook CRM Add-n Sync Message

 

 

 

 

 

 

 

 

 

 

Outlook CRM Add-n Sync Message Success

Outlook CRM Add-n Sync Message Success

 

Recently this question came up on a forum post I answered and wanted to share it on our blog also.

The forum poster did not have Outlook available and was getting the following message:

To view and refresh dynamic data, Microsoft Dynamics CRM for Outlook must be installed. If it is already installed and configured, click “Refresh from CRM” to sign in to Microsoft Dynamics CRM.  If you do not want to be prompted again to sign in, click “Save my email address and password” on the Sign In page.

KB 2556284 provides the solution by providing the following steps:

You can workaround the requirement of using the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook client by going through the following:
1.  Export the Dynamic Worksheets and/or Dynamics Pivot Tables from Microsoft Dynamics CRM 2011.
2.  Open up the Dynamic Worksheets and/or Dynamics Pivot Tables with Excel.
3. After the ADFS sign in page or the “Script is disabled” error shows in the worksheet, click on Data tab.
4. Click on Connections.
5. Within Workbook Connections, click on Properties.
6. Within Connection Properties, click on Definition tab.
7. Click on Edit Query button.
8.  Within the Edit Web Query, window you will need to do one of the following:
- Using IFD Claims authentication, the Edit Web Query will redirect to ADFS login, enter in the user’s credentials and click on Sign In.
- Using Claims authentication, continue to step 9.
9. After getting the Microsoft Dynamics CRM error, click on OK.
10. Within Edit Web Query, click on Cancel.
11. Within Connection Properties, click on Cancel.
12. Within Workbook Connections, click on Close.
13. Within Excel > Data tab, click on Refresh All.

 

Note: These steps are required every time you close and re-open the Dynamic Worksheets and/or Dynamics Pivot Tables.

Do you have an interest in building a mobile CRM application but want to leverage existing core competencies and not have to build up a iOS, Android or Win 8 environment?
There are several tools on the marketplace that will allow you to use html/Javascript or C# to build your application. It will then convert it to one or more of three popular platforms – iOS, Android, or Windows 8.

Understand that although these apps are very powerful it isn’t quite the same as building it natively.

Here are a few to take a look at:

Xamarin  - this application leverages C# and while not free except for the starter version, it is reasonably priced.

PhoneGap  - original an independent open source solution it was purchased by Adobe a short while ago. It is still open source and free.This tool leverages HTML, Javascript, and CSS.

Project Siena  - this is currently in beta but it is Microsoft’s excellent foray into this area. While it doesn’t have a built in connection to CRM as of this post date, it is possible to get it connected to CRM. Currently it only produces Win 8 applications.

After looking into these applications if you still need some help our firm build’s task specific mobile applications.

For example here is a video on a field service management application we did for a client recently.

Did your firm acquire an External Connector License for your CRM 2011 OnPremise instance? Back in the days before CRM 2013 if you created a portal that customers, partners, vendors could use to connect to the CRM system via the custom API then you needed to buy the EC license. Alternatively, if you happened to be using CRM 4 or then later 2011 Online it came with the annual subscription built-in.

With the release of CRM 2013 OnPremise and the movement to standardize the user license nomenclature etc. between the two platforms the EC for Onpremise requirement went away.

So if you already own an CRM 2011 EC license and have upgraded your CRM OnPremise to 2013 then you can use the EC license as CRM server license.

CRM 2011 External Connector License

CRM 2011 External Connector License

Has your CRM Organization moved from the old CTP Platform and now is running in Office 365? Did emails that depend on the email router to be sent out appear to be stuck inside of CRM?

The reason is that the end points changed and you need to update your email router deployment configuration. I have found that it is necessary to delete the current deployment configuration and create a new one to solve the issue.

The key difference is that you need to use the correct url – change the dev to disco

Old

  • https://dev.crm.dynamics.com/<OrganizationName> where OrganizationName is a placeholder for the actual ID of your organization.

New

  • https://disco.crm.dynamics.com/<OrganizationName> where OrganizationName is a placeholder for the actual ID of your organization.

 

Have a great day

PS. don’t forget that the organization name is Case Sensitive

If you have implemented your CRM organization and not done a sanity check of the built-in cascading relationships for the COLAC (contact, opportunity, lead, account, case) entities vs. your corporate business practices then you have missed an important step in the architecture process.

When you have a one-to-many relationship there are effects to the related entity when you make changes to the parent record. These changes impact ownership, record status/state, and access rights. You can accept the out of the box behavior or you can customize it to fit the way your organization works. For example when ownership of an Account record is assigned to another CRM user, who should own all the open and closed – activities, opportunities, cases, etc? This can have significant impact on performance tracking, access to records and customer insight.

The MSDN system has a good technical article on this subject. And although this link references CRM 2011 it is equally applicable to CRM 2013.

http://msdn.microsoft.com/en-us/library/gg309412.aspx

Dynamics CRM Entity Cascading Relationship

Dynamics CRM Entity Cascading Relationships

CRM 2013 Update Rollup 2

March 17th, 2014

Issues that are resolved in Update Rollup 2 for Microsoft Dynamics CRM 2013

  • CRM 2013 Outlook filtering does not work after you perform a quick find search.
  • When you use Internet Explorer 8, the related record dropdown is missing when a record is opened.
  • When you use the Upgrade Wizard, an error message is shown with a red flag in the System Checks window: “The product key is not compatible with the installed version of Microsoft Dynamics CRM”
  • Upgrade does not create relationship for custom activity entities to mailbox_sendermailboxid.
  • When you run the email router to process incoming email, some email may be skipped. This occurs if the email in Exchange Server has a different message class than the IPM.Note default.
  • When you try to use a view that has a condition for Owner Equals Current User’s Teams and the user does not belong to any team that has a security role, you receive an error: Invalid Argument.
  • When you click the hyperlink in a lookup field after you focus in the field, you receive a script error.
  • When you create a recurring appointment that has exactly 16 occurrences, only 15 occurrences are created. When you create 17 occurrences or more (or 15 occurrences or less), the correct number of appointments are created.
  • Microsoft Dynamics CRM 2013 has inconsistent behavior, depending on the place from which the case is resolved. When you click Resolve Case from the entity Form, the Resolution (subject) that is passed in by the end-user is replaced by the generic phrase “Resolve Case.” When you click Resolve Case from the Grid, Microsoft Dynamics CRM saves the value that was provided by the end-user. In Microsoft Dynamics CRM 2011, the value was provided by the end-user and not overridden by CRM.
  • When you view completed activities, such as email, you cannot select any text on the record. This includes the body control.
  • Users of the offline edition of the Microsoft Dynamics CRM Client for Outlook cannot configure their Offline Scheduled Sync settings under Personal Settings.
  • Depending on the placement of an option set field in a section of the Microsoft Dynamics CRM 2013 form, the number of visible options is limited, and the user has to scroll to see the remaining options.
  • After you upgrade Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM 2013 or import Microsoft Dynamics CRM 2011 appointment customization, you receive a pop-up error message while you are saving appointments:
    There was an error with this field’s customized event.
    Field:crmform
    Event:onsaveError: Object doesn’t support property or method ‘Form_onsave’
  • Field alignment setting is not respected on Microsoft Dynamics CRM 2013 forms.
  • You cannot customize YomiName fields because the detail form does not display.Copying and pasting multiple lines of text from a Microsoft Word document to the body of a Microsoft Dynamics CRM email activity record causes additional line breaks to be inserted between each line.
  • When you use Chrome to view duplicate detection rules in Microsoft Dynamics CRM 2013, the criteria are not shown every time that you open the record. You may have to close and then reopen the record an undetermined number of times before the criteria are shown.Outlook client is unresponsive during startup.
  • When you save or send an email from the Microsoft Dynamics CRM 2013 web client in an email activity that had a template inserted, the body is saved or sent with nothing in it. If you edit the email body after you insert the email template, or if you use the insert template button on the email editor toolbar, the body is saved or sent correctly.
  • When you use Internet Explorer 8, the related record dropdown is missing when a record is opened.
  • After you upgrade or install Microsoft Dynamics CRM 2013 when you create a telephone call activity from an existing contact or lead, the telephone number field is not populated correctly. This behavior is different from what occurred in Microsoft Dynamics CRM 2011.
  • Outlook saved views are not sorted alphabetically as they are in the web client. Outlook saved views should be sorted exactly as they are in the web client.
  • Deadlocks occur when an Associate request is called to add users to teams.
  • Custom entity grid icon is not visible in Outlook.
  • Lots of notes cause the focus to be lost when you create new notes.
  • Custom reports that aggregate with a groupby on OptionSet fields display: #Error.
  • When a user searches for a string of numbers that exceed the upper bound of the whole number column in Microsoft SQL Server, the following error is returned to users, and the search is ended: “Invalid Argument”
  • Field security on check boxes causes JScript error when you save.
  • When you have a web resource that should be shown across the width of a section, and you change the visibility of the web resource, the width is reduced by half.
  • Incorrect “Do Not Allow” notification is generated on Phone Call/Email.
  • Subgrids update continuously with a “Loading…” message.
  • Consider the scenario in which using Microsoft Dynamics CRM 2013 affects synchronous plug-ins or synchronous workflows to perform an update of the StateCode and StatusCode of Activity entity. The StateCode and StatusCode action is taken Post-Create synchronously then an exception occurs on the Save. When the same plugin code registered asynchronously, it will process and complete without error.
  • Query Builder error occurs when you use addCustomView that contains a related attribute.
  • When you set IME mode on an attribute on an entity to ACTIVE, the IME mode is not honored. This occurs with Single Line of Text, Multiple Lines of Text, and other attributes that are bound to input elements or text area elements.
  • After you paste a numbered list into the email body control and convert the pasted content to a bulleted list, the bullets are misplaced above the selected text. The bullets will appear on their own separate line, even though there is no line break. Additionally, the text cannot be moved up to the bullet so that both the text and the bullet appear on the same line.
  • Personal View is removed when Show Selected Views is used on Dashboard Grid after redraw.
  • Time Format selection is not reflect correctly in setting.
  • Unexpected format changes occur when you create mail messages from an email template.
  • Users who have no Create permissions but has Read, Write, Append, and Append To permissions cannot select an Entity record that has an N:N relationship. This occurs for both custom-to-custom and system-to-custom entities.
    Unable to get property ‘get_element’ of undefined or null reference
    SCRIPT5007: Unable to get property ‘get_element’ of undefined or null reference
    File: inlineeditcontrols.js, Line: 1, Column: 89186
  • When you import an updated solution that contains lots of entities, the import is not completed in Microsoft Dynamics CRM 2013.
  • If a user presses the Enter key in the body and then presses the Delete key when the user is replying to email activity records in the application, a line break is inserted into the body of the form.
    The mailbox (CRM User) has been disabled for synchronizing appointments, contacts, and tasks due to unknown error. The owner of the associated email server profile (Profile Name) has been notified
  • When you review Microsoft Dynamics CRM client for Outlook tracing, the tracing incorrectly suggests that an item was being updated when in fact it was being created in Outlook from a synchronized CRM Microsoft Dynamics CRM item such as a contact, appointment, or service activity

 

Source : http://support.microsoft.com/kb/2919956