Skip to main content

How to get item ID in Calculated column using Document ID

In my previous post, I explained about a new feature "Document ID Service". Using this feature, we can resolve one of the basic problems we had for long in SharePoint history. And that is the title of this post!

There is no way you could get the item ID in a calculated column using ID field. When you try to create a calculated column, it is very evident that ID column is not listed under fields. However, if you go ahead and use ID column, it will not prompt any error.

For example, I have created a calculated column and it's formula is =[ID]. When I add a new item, this column returns 0 as shown below.
Calculated Column using ID field
However, if you edit an item, the calculated column shows the correct value. This has been the problem since MOSS 2007 version (I started my SharePoint journey with 2007 version, so I don't know about prior versions). One workaround was to create SharePoint Designer to do this calculation and set the value.

Now with Document ID feature, we can do a small tweak and get the item ID. If you notice carefully how Document ID is formed, the item ID is suffixed at the end. So we'll use Document ID column to extract the item ID. Now create a calculated column and if you observe, Document ID column is listed over there! This is how my formula looks like:
Formula

I'm doing string manipulations to get the item ID. One assumption I have made here is that the item ID will not touch 5 digits. I think this hard coding can also be worked out to make it generic.

Now when I add an item, this calculated column shows correct item ID as shown below.
Calculated Column using Document ID field

Instead of implementing SPD workflow, we can just use this out of the box feature to get item ID.

End Notes: This solution is not tested for all cases. So use it as appropriate. Obviously this is applicable only to Library and not to the List.

Comments

Popular posts from this blog

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this:

data: { "__metadata": { "type": "SP.Data.ListNameListItem" }, "Title": "First Item", "PeopleFieldId": "4" };

The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns.

How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post!

The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in people picker, I…

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post.

Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style.

When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style.


I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one.

Default:
This view, as name suggest, is the default style in a view. This is one of the widely seen style in SharePoint site. This is how it…

Difference between Choice and Lookup fields in SharePoint

When you have to provide users an option of selecting a value from a list, you can go for a Choice field or a Lookup field. Have you ever wondered which one to use and when? Which option should be chosen over other? To address these questions, one need to understand the differences between these two data types in SharePoint. This post outlines these differences to help users decide the appropriate column type based on their needs.

FactorChoiceLookupPermissionTo add values to a Choice field, you need minimum Design permissionTo add values to a Lookup field, you need minimum Contribute/Add permissionChanging existing ValuesIf you change a value in a Choice field, it does not affect the existing values. For example, let us say one of the values was NY and there are items with this value. If you change it to New York in the field schema, it only affects the new values. All existing values will retain NY.If you change a value in a Lookup field, all the existing rows reflect the new value,…