Skip to main content

Show\Hide columns in the SharePoint default list forms

Here are two cases that I face in the daily work with SharePoint which I find very common and would like to provide some technical details.

1. Hide Yes\No column
If you want ho hide an Yes\No column inside content type, surprisingly you find that you can't.

Or to be more specific, the SharePoint interface won't allow you to do it.
I'm not sure why is that limitation but тхис is technically supported by SharePoint.
Here is a JavaScript that modifies the column visibility. You just need to run it with user who have appropriate rights.

var context = SP.ClientContext.get_current();
var siteContentTypes = context.get_web().get_contentTypes();
// add the GUID of you ContentType
var myContentType = siteContentTypes.getById("0x010100185E5E735545B942852F513AEB77B51C");

var fieldLinks = myContentType.get_fieldLinks();
context.load(myContentType);
context.load(fieldLinks);

context.executeQueryAsync(
    function (sender, args) {

        var listEnumerator = fieldLinks.getEnumerator();
        while (listEnumerator.moveNext()) {

            var field = listEnumerator.get_current();
            //Add here the internal name of your column
            if (field.get_name() == "DTSIsApproved") {
                field.set_hidden(true);
                //field.set_required(false); // OR make the column reuqired 
                myContentType.update(true);
                context.load(field)
                context.load(myContentType);
                break;
            }
        }
        context.executeQueryAsync(
              function (sender, args) {
                  console.log("Column is updated!")
              },
             function (sender, args) {
                 console.log("Error:")
                 console.log(args)
             });
    },
     function (sender, args) {
         console.log("Erro:")
         console.log(args)
     });


2. Show one column in the Display Form, but hide it in the Edit Form
One well described method in the blog posts is to use JavaScript or css to hide the column in the Edit\New form. This approach works but has a huge disadvantage.
In case you have Document library and the users open the file with the Office client (Word, Excel, ...) the column will be visible!

The correct way to hide column in New or Edit form is to use the column's settings ShowInEditForm, ShowInDisplayForm.
Here is a JavaScript that modifies these settings:

var context = SP.ClientContext.get_current();
var list = context.get_web().getList("/sites/demos/Docs");
var fileds = list.get_fields();
var myColumn = fileds.getByInternalNameOrTitle("DTSIsApproved");
context.load(list);
context.load(fileds);
context.load(myColumn);
context.executeQueryAsync(
    function (sender, args) {
        if (myColumn) {
            myColumn.setShowInDisplayForm(true);
            myColumn.setShowInEditForm(false);
            myColumn.setShowInNewForm(false);
            context.executeQueryAsync(
                  function (sender, args) {
                      console.log("Column is updated!");
                  },
                 function (sender, args) {
                     console.log("Erro:")
                     console.log(args)
                 });
        }
        else {
            console.log("column is null:")
        }
    },
     function (sender, args) {
         console.log("Error:")
         console.log(args)
     });



PS: Your feedback is highly appreciated.

Comments

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:
1.Add this references

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
2.Add the following control declaration


      <wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem: 
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."



Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

Solution:
It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
 - it supports columns with same Display Names.
 - you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
   Type: Multiple lines of text
   Internal Name: MyProjectDescription
   Display Name: Description

 Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…