New answers tagged

2

The most important questions are: Will choices change often (e.g. more than once a year)? (if yes, a lookup field may be better). Who will update the choices? Only one "skilled" SharePoint power-user who will have "Manage" permissions on the list? Or many users, who should not have elevated permissions (in the latter case, a lookup field may be better). ...


2

The advantage of creating it as a lookup column versus a static column is you can delegate the maintenance of the column to other users who might not be site admins. You give them the ability to Contribute to the underlying list to add/remove values as necessary versus having to elevate permissions for them to site columns.


0

As far as I know, this isn't something you can achieve. First of all, let's start with a little clarification. Bear with me but I think there is a little confusion in your question, so probably is better if I start with some assumptions. Fields and content types in SharePoint are separate entities. To keep it as simple as possible, consider a content type ...


0

Using the declarative (XML) based approach to create fields has always frightened me, and here's a new reason. I really encourage people to use a pure imperative/C# approach (when possible, i.e. very often): creating a feature event receiver with code that creates artefacts by the mean of the server-side OM. That way, you control exactly what happens ...


2

I wouldn't touch the database. The SharePoint DB is very complex and you can break everything running queries on it. If designer doesn't work for you, use PowerShell: $webUrl = "http://theUrlOfYourCollection" $columnName ="My column to delete" $web = get-spweb $webUrl $field = $web.Fields[$columnName] $shadowField = $web.Fields[$field.TextField] # ...


0

You need to carefully examine the ulslogs. And post back here with findings, otherwise it is total guess work.


0

For the list that you want to add the column to: List Settings --> Title, description and navigation Select the option to use this calendar for Resource Reservations. (If you do not see this option, then you need to go to Site Settings --> Manage Site Features and turn on Group Work Lists. If you do not see that feature, your admin needs to turn it on in the ...


1

Content Types work in that way and propagating changes is a good way to apply changes to all inheriting objects (List/Libraries). You should not afraid because it requires higher privileges to do so, so only responsible person would be doing that. You should wisely set up permission that will ensure only responsible persons can make necessary changes. ...


1

I've just worked through your scenario in SharePoint online. Did 1. through to 4. Description is hidden in my custom Issue list form. Then I edited the native Issue CT and made the Description field required. clicked "Yes" to update all content types inheriting from this type opened a new issue in my custom Issue list The previously hidden Description ...



Top 50 recent answers are included