Advertisements

Disable SSL check for enabling Data Encryption in CRM 2013

By now many of you might have already worked with Data encryption feature in CRM 2013. In case you are not aware of this new feature, I suggest you go through the following link.

https://community.dynamics.com/crm/b/crminogic/archive/2014/03/27/data-encryption-in-crm-2013.aspx

Isn’t it really simple to just go to Settings->Data Management  and enable Data Encryption with the key of your choice. Well it is. However the moment you try to do so and your CRM website is not configured with SSL certificate, you get the following error.

image

So thinking that you would need to request a certificate and bind with CRM website? Well if possible i strongly recommend you doing the same. If may sound tedious to get a certificate for this but actually you end up protecting your own sensitive data and account passwords.

However if you are not willing to do the same, you can do the following workaround.

Open SQL and connect to MSCRM_Config database.Run the below query. Remember to Restart your IIS after executing the query below. Hope this helps!

 

UPDATE [MSCRM_CONFIG].[dbo].[DeploymentProperties]
SET [BitColumn]=1
WHERE ColumnName='DisableSSLCheckForEncryption
Advertisements

Get PrivUserGroup specific to your CRM Organization in Microsoft Dynamics CRM

Hi, recently in my project, I had a requirement to enable Data encryption feature that is new to CRM 2013. While enabling and proving the key, we got an error – “The user account for enabling Data Encryption should be a member of the PrivUserGroup in active directory.

We had to contact our AD support team and they asked for the PrivUserGroup specific to our organization. How would you actually know what. Well there is way.

Open  SQL and in your organization database, execute the following query

select ReportingGroupName, SqlAccessGroupName, PrivReportingGroupName from Organization

Thinking where is the privusergroup in this query? No worries. In the result you would find in the name of each of the above queried Groups a GUID which is same for all the three groups. For example:for the privreportinggroup the value would be similiar to the format below.

<Your domain name>\ReportingGroup {d367569e-489f-46ea-b427-eaab03087d7d}

So all we needed is to provide the GUID – {d367569e-489f-46ea-b427-eaab03087d7d} for the privusergroup to the AD Team and they were able to help us out.

 

Hope this helps!

Issue with Dynamics CRM 2013 SP1 upgrade after database import through CRM import wizard.

Recently in my project, i had to prepare a demo where we were going to show to the customers, the new service module enhancements. Since we needed our existing data to show the demo, we took a backup of our dev. environment and then restored into our POC environment. Since our dev. environment was with update rollup 2, we made sure that the demo environment also has the same update rollup.

We imported the database smoothly into our new environment and then applied CRM 2013 SP1 update. However we found that new entities shipping with SP1 update like Entitlements, SLA’s as such were not there even after the upgrade. We could not find them even through advanced find. However strangely enough those entities were all in the organization database. We tried with lot of workarounds including uninstalling and reinstalling CRM and then applying the updates as such. But still it didn’t work out for the restored organization.

Finally when we contacted Microsoft Premier Support, they update us that Microsoft is already aware of this issue and they have made the hotfixes available to install through the “Install Product updates” under the “Administration” section.

image

But when we tried to install the updates, it failed due to some of the system charts (“Top Customers”, “Case Mix By Priority”, “Case Resolution Trend”, “Activities By Month Due”) on Opportunity entity were deleted by the previous Rollups (1 or 2) in our all environment which prevented from running the below Product Updates.

Solution: MS engineer asked us to run the some SQL scripts in Demo Org and run the above “Install Product Updates” and all the missing forms in the new service module forms/views were re-created and all works fine now.

I am unable to share the SQL script because of legal considerations. However thought of sharing my experience since we lost sufficient time while resolving the issue. Hence if you face similar kind of issue, contact MS Support for the quick resolution.

Hope this helps!

Customization changes in Microsoft Dynamics CRM not working with latest version of Chrome

Cross browser support in Microsoft Dynamics CRM was a great feature. Wonderful isn’t it that you can open most of the browser(s) (check for the supported list in MSDN) and your CRM would continue to work seamlessly. And in recent months, I find lot of users have shifted to Chrome while they browse CRM.

But recently, during one of my implementations for a customer, we faced a strange problem while using chrome. We were trying to edit the filter criteria and of the views and hide and show some of the fields on the form. Did all the changes and then saved and published the customizations. Whoo! some it took. But alas when we browsed CRM, we can see none of the changes affected. When we went back and checked the customizations, we found that none of the changes we made are actually there.

Well let me try to explain couple of the scenarios here.

 

I have an entity called Test entity 1 and as you can see in the screenshot below, I have opened the form for the same in Chrome and have unchecked the box for ‘Visible by Default’ for ‘test field 2’. I now save and publish it.

 

image

However when i open the editor back, I can still see the ‘visible by default’ checkbox in checked state.

image

Similarly, editing views and a whole lot of other customization stuffs wont work in Chrome. I have tried this in MSCRM 2013 with UR2 and Chrome version 37 & above.

So as of now guys stick to IE before any UR releases by Microsoft to fix the same.

 

Hope this helps!

How to get name of the Logged in user in Microsoft Dynamics CRM 2013

In Microsoft CRM 2011, many a times we used had to get the name of the logged in user using client side script. Xrm.Page.context.getUserId() used to give us the guid of the user. But alas as simple as it may sound, getting the user name meant to query the user entity with the guid and then get the user name.

Well long time we wished if Microsoft is listening to our prayers, and indeed it has. We now have the method Xrm.Page.context.getUserName() that servers our purpose.

 

Hope this helps!

Using getClientUrl() in CRM 2013 and how is is different from getServerUrl() – Microsoft Dynamics CRM

Recently in my training sessions, i am coming up with this question very frequently. Hence thought of sharing. I am pretty sure that many of you might already know this by now. However this post might be of help to somebody trying their first hands on CRM 2013 and having this question in mind.

First let’s shift our focus to getServerUrl(). Well first of all even if you are in  CRM 2011 and you have upgraded to Update Rollup 12 and still using this method, please do not use the same as it has been deprecated.

Now when we used getServerUrl(), it used to return the Url that is registered in the CRM deployment Manager. However there are some situations where the user might be accessing the application using a URL different from the base server url such as an IP address or a domain alias. In these situations it will be cross domain calls and hence it would fail.

getClientUrl() as the method name itself suggests, does not blindly return the base server url. Instead it looks at the url that was used to access the CRM application. Hence no cross domain issue.

Isn’t it great to get rid of the access denied error messages that we used to get during rest calls while using getServerlUrl() !

 

Hope this helps!

{Error} Public assembly must have public key token – Microsoft Dynamics CRM

Hi,

Faced this error very frequently during my early days with MSCRM. With all my enthusiasm, I would build a plugin and register it in my CRM. Oops! The plugin registration tool throws me an error.

Once of the reason why this error is being thrown is probably because you have forgot to sign the plugin assembly. I have seen that error usually comes up when you plugin dll is referencing other assembly and you do an ilmerge but forget to sign the merged assembly before uploading it in Plugin registration tool.

Hope this helps!