Contextual filtering in sub grids is a very common requirement, which is not supported out of the box in CRM. People use unsupported JavaScript which works till January update 1 and for spring release it stopped working. But if we understand why it will not work in spring release, because of new form structure and change DOM, document.getElementById stopped working.

JavaScript method which will work in January Update and Spring release 

The above function will return the object in both January Update 1 and Spring release. Now any sub grid can be filtered in January Update 1 and spring release both. Here is the method:

But again this method is unsupported and it might stop working in subsequent releases of dynamics CRM online. This has been tested on Chrome and IE for CRM online for January Update 1 and spring release both.

Happy programming in Dynamics CRM online

Issue – Workflow with Email Messages having
Record Dynamic URL

• 
  If Workflows contains send email functionality and there are dynamic Record URLs, such solution doesn’t get imported from CRM 2013 to CRM 2015 directly because there are no metadata attribute information available for Record Dynamic URL attribute and it will fail the importing solution, although organization import will work but that will cause such workflows in draft mode.

How to Trace

To Trace such issue, download the solution having all the Processes in CRM 2013 and extract the zip file, open the workflows folder, rename all the xaml file as xml by a simple console command

Rename *.xaml *.xml

Open all these xml files in a Visual Studio Solution and use short cut ctrl + shift + F to find in all files. Search for “!Process_Custom_Attribute_URL_”

This attribute will show all the files and locations where Record Dynamic URL has been used

Workaround/Resolution

• 
  To resolve this, once you get all the workflows, open them individually in CRM 2013, deactivate them, remove the Record Dynamic URL property from Email body and then save and Activate the workflows
• 
  Publish the solution and then export it, it should get easily updated in CRM 2015 now
• 
  Once imported, open all those workflows, deactivate them and then add the Record Dynamic URL back again in the Email body
• 
  Activate the workflows and publish the solution 

Issue – JavaScript Removed Methods

Removed methods are either obsolete or replaced with other methods. You should make sure these methods aren’t used in your scripts. The following methods were deprecated with earlier versions of Microsoft Dynamics CRM and are no longer present in the current version:

getAuthenticationHeader

This method supported use of the Microsoft Dynamics CRM 4.0 web services, which no longer exist.

getServerUrl

This method was replaced by getClientUrl

isOutlookClient

This method was replaced by client.getClient

isOutlookOnline

This method was replaced by client.getClientState

How to Trace

To trace JavaScript removed methods, download the solution having all the web resources and after extracting all the web resources search for all above mentioned 4 methods.

Resolution

Before doing actual upgrade, replace above methods with appropriate methods

This article is an ongoing article, and I will keep on updating as in when I get the information.

Issue – Security Tab missing after Upgrade

Previous CRM 2013 solutions doesn't have Users and Roles under Security tab, while in CRM 2015 they are moved under Security tab. this tab will get missed if site map is edited in CRM 2013 and then solution gets imported to CRM 2015.

Resolution

Copy the sitemap from CRM 2015 new organization and get the security tab back in CRM 2015 after upgrade

A scenario when you are trying to import a solution where you have created a quick view form and trying to consume the same in some other entity's form. If that entity appears before the entity for which you have created the quick view form. For example:

• If there is Account entity quick view form which you have newly created and used on Contact entity as part of same solution. When you try to import that solution it will give you error that Form with Id '<GUID>' does not exist. Unfortunately there is no direct solution to this problem. if your quick view form's entity customizations come on the top of entity's customizations of entity on which you have consumed that Quick View Form, it will not create any problem. To Solve this problem you can nail it down in two ways, either create two different solutions and import the solution having quick view form first. The other solution could be to edit the customization.xml and move the whole entity node having "Quick View form" on top of entity consuming that form, save it. Zip and make your solution file to make it work. Note: This is not a suggested solution as this is unsupported but can be used as a workaround.