If SharePoint on-premises, what's exact CU version:
Expected or Desired Behavior
docSet.CreateFolder(folderName) should create a folder within the custom Document Set even if a column in the SharedFieldCollection contains a space in field name.
Observed Behavior
This error occurs when the Library contains a custom Document Set Content type where one or more columns in the SharedFieldCollection contains space (X000) in the internal name.
We found a work-around as long as the custom Document Set Content type is defined at the site collection level. If defined in Content Type Hub the work-around does not work even if we un-publish the content type.
The work-around is described in the StackOverflow thread mentioned below.
The source code used to observe the problem is described in the StackOverflow thread mentioned below.
User is using CSOM code to create folder. Got following error when CSOM code is used to create new folder. One or more field types are not installed properly. Go to the list settings page to delete these fields.
Which PnP repository to report the issue?
Category
[X ] Bug [ ] Enhancement
Environment
[X] Office 365 / SharePoint Online [ ] SharePoint 2016 [ ] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
Expected or Desired Behavior
docSet.CreateFolder(folderName) should create a folder within the custom Document Set even if a column in the SharedFieldCollection contains a space in field name.
Observed Behavior
This error occurs when the Library contains a custom Document Set Content type where one or more columns in the SharedFieldCollection contains space (X000) in the internal name.
We found a work-around as long as the custom Document Set Content type is defined at the site collection level. If defined in Content Type Hub the work-around does not work even if we un-publish the content type.
Steps to Reproduce