Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

CRM 2013: Disable click to call integration or add custom phone integration logic Part 1

I recently installed CRM 2013 Servers on my customers Server. Major Thing that was bugging me and the customer was that in CRM 2013 you are not able to completely turn off the click to call integration with Skype or Lync.

It makes me sad that Microsoft did not provide a way to completely turn this feature off. I believe there are many customers out there which do not use Lync nor Skype.

The requirement of my customer was that if they click on the phone number e.g. in a contact that they only want to edit the phone number and not start a phone call right away.

This made me look for alternatives to turn this feature off. Checking the JavaScript of the CRM 2013 system I was able to track down that at some point the following method is defined and executed:

openPhoneWindow

Searching all the files of the CRM 2013 installation files I found the following occurences:


In the OnLoad of the contact entity I added this simple workaround:

Mscrm.Shortcuts.openPhoneWindow = function() {return;}

The result is that now if the user clicks on the phone number it won't open a new browser window and try to call the phone number via Skype or Lync.

The only thing that it still does it will jump to the middle of the contact form and offers the user the opportunity to add a phone call activity.

This behavior may also not be desired and I will look if I can find a solution for this as well and keep you up to date with a new post hopefully soon.

Comments

  1. Totally agree Microsoft was not thinking this through. I will try your suggestion.
    Thanks for publishing your effort, Brian

    ReplyDelete
  2. Hello Andreas, Thank you for these insights. I was looking for a way to prevent the phone call activity and by using your approach on a different function it seems to work. Mscrm.ActivityContainer.focusOnPhoneActivity = function() {return;}
    Also, I did not add it as an onload function, but just adding the library was sufficient.

    ReplyDelete

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu

CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of