Tag Info

New answers tagged

0

The columns defined as unique (so the BDC identity was built on that colums) were not unique in the sql view, that why I had not unique BDCIdentity.


0

To be more precise.. Again activate the content type feature then delete all list and library which refer to that content type and even from all the recycle bin (Site and Site collection both). Then deactivate feature it will remove content type.


0

You can create content types at site collection level and add it to respective document libraries. Now if you change the content type in Site Collection level, the changes will get reflected automatically in library level (provided you haven't updated the content type at list level) Content Type has following properties EditFormUrl NewFormUrl ...


0

You cannot do this with the UI, but you can do it with PowerShell or C# code. The internal names of the columns are fRecurrence and fAllDayEvent and the property you want to set is Hidden. So you can update the associated FieldLinks of the Content Type with code like this (PowerShell): $ctype = $myList.ContentTypes["Event"] ...


1

The code is getting the content type from the root site collection and adding it to a List named "Shared Documents", in root site. Moreover, it is looking for the same named list in all sub sites. If it finds one, it is adding the content type to the list. If your requirement is to add the content type to a particular list in a single sub site, you can ...


0

Finally I was able to create OneNote documents without issues using Sharepoint 2010 workflows instead of Sharepoint 2013 Workflows. The error only occurs when a SP2013 WF creates a document with custom content type and the associated template. The same functionality (the 'Create Item' command to be precisely) works in SP2010 Workflows.


2

If you are adding your site columns and content types to the app project, these will get deployed to the App Web, not the Host Web (site you are cheking for the content type). For more information around the subject check this link. If you want to deploy content types to the host web, you will need to use the Remote Provisioning Patter. Check provisioning ...


1

Issue in my case seems to occur when you create new content type based on page content type but don't add any custom columns to the content type. Once you add one additional custom column to the content type in addition to Page content type default columns issue is gone.


0

I did find this Google Books result that appears to indicate that the option is extraneous and serves no purpose. (From the link, scroll down slightly to the "An extra option" sidebar.)


1

Usually when you do retract on Visual Studio it deactivates features first. If your content type is already being used in some library or list, this content type will not be deleted. First of all you should delete every list with this content type, even from the site collection recycle bin (IMPORTANT!). After this you should successfully retract you solution ...



Top 50 recent answers are included