CRM 2013 Migration: Custom entity form issues - dynamics-crm-2011

We have migrated to CRM 2013 from CRM 2011. we are facing the following issues post Migration.
Onload of one of the custom entity form, it was giving error in the internal javascript(JsProvider.ashx).
Error-Line: 2
Error: Object doesn't support property or method 'get_disabled'
And also noticed that While saving the form customization of the same entity getting error permission denied. The error was on the line window.top.opener.auto(Mscrm.EntityTypeCode.SystemForm).
Couldn't understand why this is happening? The user has Administrative privileges. Have anyone faced this kind of issue?
Note- THis entity has multiple forms and this issues are happening only with two forms.

Seems like a compatibility issue for the forms. Were they imported from CRM 2011? In that case you can open a support case with MS or recreate them using the CRM 2013 GUI.

Related

Sharepoint integration for entity kbarticle on CRM 2016

We have had a CRM 2015 OnPremise which used standard Sharepoint integration for several entities, among others the entity "kbarticle". Then we upgraded to CRM 2016. Afterwards, we have problems with the document upload for entity kbarticle. If I click on "Documents" on the left menu of a kbarticle record now, the CRM tries to generate a sharepoint folder - but with the wrong URL:
I would expect a new folder for the record at "mysharepoint/sites/mysite/kbarticle/MyRecordName_[GUID]"
But the CRM takes: "mysharepoint/sites/mysite/kbarticle"
As you can see the CRM does not try to generate a subfolder for the record, but takes the parent folder only. Furthermore when I click "Ok", the error message "Both absoluteurl and relativeurl cannot be null" appears.
This issue does only occur for entity kbarticle and only on CRM 2016. I checked the sharepoint integration settings. All seems to be ok.
I know that the entity kbarticle is obsolete in CRM 2016, but does anybody know if the issue can be solved?

Customize the Add Location Box : Dynamics CRM 2016

I have a requirement where I need to auto fill the values in the Add Document Location Box when a User clicks on Documents in the Dynamics CRM 2016. I don't think there is an out of the box way to do this. Any hints or suggestions are appreciated.
I tried creating a sharepoint document location record on creating the record. When I click on Documents, it tries to find the URL for the location and gives an error that the location does not exist. I had hoped that the sharepoint folder will be created once the Sharepoint document location record has been created and associated with the record but that is not the case.
In case you have ever faced this problem, or if you have an alternative solution, please let me know.
Thanks!
In CRM 2016 you can enable server-based SharePoint integration. As a side note, in previous versions of CRM the List Component was required for the functionality you describe, but that is now deprecated.
When clicking on Documents on a SharePoint enabled record, you will see a popup similar to the following after enabling the server-based SharePoint integration:

Pulling CRM 2011 data into Sharepoint 2013 using a webpart?

I've been hunting all day trying to find some good examples/tutorials on how to pull data into Sharepoint 2013 from CRM 2011. The best thing I have found so far is a SP2010 example, but with VS2012 and SP2013 it seems like so much has changed, and trying to make that tutorial work isn't going well thus far.
I have no experience with SP; with CRM I have used the CrmSvcUtil.exe in the past to generate a class and use that within a .NET app in order to view/update data in CRM. I tried implementing this into my Visual Web Part, but I need to be able to add connection strings to the config file which it doesn't seem are recognized by the web part. I see that I can add a service reference to the CRM Organization service but I'm not sure if/how I can use that to query data. Any help is appreciated, or if anyone could point me in the direction of some good documentation. Thanks!
You have got couple of options.
(1) Use SharePoint 2013 client API.
Consume the client API from your CRM plugin / custom workflow to update the crm data to SharePoint 2013.
(2) Consume SharePoint 2013 webservices from CRM plugin / custom workflow.
I don't think this works in sandbox based solution.

InvalidPluginExecutionException dialog does not show up - CRM 2011

I have a Plugin on the Creation, Updating, and Deletion of the OpportunityProduct entity in the CRM 2011. I want to through exception on the success of some operations, means want to display dialog. It is working fine for Update and Delete. But it is not working fine for the Creation of OpportunityProduct, it is not throwing exception in the dialog. It is showing Exception: “An error has occurred, Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solution or contact your organization’s Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.”
Message : Create
Primary Entity : opportunityproduct
Action: Pre-Operation
Execution Mode: Synchronous
I think this is an internal issue that relates to how CRM treats compound entities such as opportunity product.
To verify this behavior you should put breakpoint in your code and inspect the context depth and parent context to understand if the create event is indeed a child process or the opportunity.
If so you might be able to re-register the plug-in the opportunity and try to somehow throw the error from there.

Using SPIF with custom Content Types

I'm using Sitecore's SharePoint Integration Framework to get items from a SharePoint 2010 installation. The list I want to import is made of an custom Content Type. Selecting the list and mapping the fields works fine. When the items are imported an error is thrown.
Sharepoint Provider can't process tree
Exception: System.ArgumentException
Message: Item has already been added.
Key in dictionary: 'Customization' Key being added: 'Customization'
Has anyone experienced this error before?
I had the same issue. After being unable to solve it I contacted SiteCore support who supplied me with a hotfix to the SPIF framework.
This fixed the problem for me.
I am using SPIF version 111115.

Resources