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.
Related
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.
I've recently installed the "CRM List Component" on a "Online SharePoint", but there are some problems when documents are added.
I'm getting "The document records could not be loaded from SharePoint. Try refreshing the grid. If the problem persists, contact your system administrator" error when adding any kind of document.
When I restart the page, the "CRM List Component" view isn't shown anymore and I see the complete SharePoint instead of the normal "View".
I've downloaded the latest "CRM List Component" on the Microsoft Site and even tried to add a new "site Library" (contact2) and it doesn't work on other "Site Libraries" too.
Has anyone encountered this problem?
If so, is there a way to resolve this?
The weird thing is, that I've done this for other customers and there it seemed to work correctly.
But I can't delete an "Online SharePoint" environment and start from scratch as it is a new environment created by the customer.
Apparently I’ve solved the Issue Myself after some research. The language of the User who created the SharePoint was different from my “SharePoint”-user. When I changed the language of my User, the problem seems to be disappeared. I guess this issue won’t be solved in the next releases of the “CRM List Component”? I’m hoping that this answer will help out other Users!
It is not always feasible to keep user's language same as site collection language. There can be a requirement to have alternative languages enabled on the site collection, where integration component is deployed. Instead of enforcing site collection language you can set the integration component language to be always same, regardless of the user language settings. This can be done by adding for example UICulture="en" Culture="en-US" attribute to the Page directive of the affected page CrmGridPage.aspx.
You can access CrmGridPage.aspx by unpacking the component's .wsp file as CAB archive. Then edit the page, archive back into CAB, rename into wsp and deploy.
Having a problem deploying a list instance via a feature, which should really be a noddy task, I know. I have come across many a post with the same issue, but there is no resolution.
I created the list in the UI with content and views.
Exported the site template as WSP.
Imported into Visual Studio the list instance, pages module and property bags.
Copied into my new solution.
Deploy list instance as a site-scoped feature.
List deploys fine with content and views. However, I receive the following error when trying to add a new item: “Unable to find the default new form for list”. The same applies for editing items.
Strangely, deploying via a web scoped feature works just fine.
I am thinking that this is probably something quite simple but cannot see it nor find a satisfactory resolution.
Many thanks in advance.
I discovered almost the same thing this afternoon, and solved it. For some reason the schema.xml has an empty Forms tag. You need to replace it with the stock forms tag as described by Microsoft - I wrote it up here;
http://notes.jonbeckett.com/2012/04/20/missing-forms-schema-with-sharepoint-2010-visual-studio/
The Microsoft page I discovered it on is here;
http://msdn.microsoft.com/en-us/library/ms459356.aspx
I have deployed an SSRS 2008 R2 project into our SharePoint Integration. This worked no problem. I then wanted to add report parts. I converted the DataSource and DataSets to Shared Components and re-deployed. No problem. I then selected the parts that I wanted to publish. Now when I deploy the project I get the error message:
Warning : Referenced item ReportsTo doesn't exist at http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.
The item ReportsTo is a part that is trying to get published. This has me a little confused. I was under the impression that the rsds file type is soley for DataSources. Given that the path that is in the error is Datasets should it not be looking for a DataSet file?
Any help in resolving this to get the parts published would be greatly appreciated.
I am working in BIDS 2008 R2 not Report Builder
UPDATE:.. After Reviewing the Logs on the Reporting Server I noticed this.
GetPropertiesAction(http://dev-sp01/sites/ThriveReporting/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
It looks like it is trying to merge the Site name with the Fully Qualified Path to the Reports Parts. In BIDS I've tried to change the Report Parts path in the deployment properties to the relative path to the Site Name provided, but it errors out and requests the Fully Qualified path. It would seem that this might be a bug.
So to Recap
When trying to Publish Report Parts
1) Bids Gives me the Warning:
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
Where ReportsTo is a Shared Dataset, so I beleive this should be looking for an rsd extention. In the Log there is a corresponding action for this but not error
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
GetItemTypeAction(http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds).
2) Reporting Services does not appear to be creating a path correctly to access a Report Part during deployment.
GetPropertiesAction(http://dev-sp01/sites/CompanyName/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
From Microsoft, I am submitting Feedback now.
Hi Matt,
I can reproduce the issue. It seems to be a known issue.
I would suggest you submitting a feedback at https://connect.microsoft.com/sqlserver.
Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.
Thanks,
Jin Chen
Jin Chen - MSFT
UPDATE:
Please go to this link and vote this issue as important so that it will get looked at sooner.
I'm in the process of doing an upgrade from SharePoint 2007 to 2010 using the database attach method.
During the database upgrade I'm getting the following error:
Feature upgrade incomplete for Feature 'PublishingSite' (Id: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') in Site 'http://intranet'. Exception: A duplicate content type name "Resource" was found
I've had a look around and found two possible solutions, but I wanted to know if anyone has tried these and which one (if any) worked.
The first solution is from TechNet which suggests renaming the "Resource" content type as there is a name conflict with the new 2010 content types.
The second solution suggests deactivating the Publishing feature and deleting the "Relationship List" list.
I'm a bit nervous about trying them as both seem to have the potential to break the site.
Thanks
I ended up attaching the database to the Web Application and it turned out that the site still worked, except for some reporting services web parts. I replaced them with the latest version and all seems well.
I followed the Technet solution and changed the name of the content type. In my case, both were called "Resource", I changed one to "Group Resource" and everything was great after that.