Skip to main content

Multiple Lines of Text column value is blank in SPD Workflow

This is a strange behavior I observed recently.

Let's say you have a List with Multiple Lines of Text column. In the column setting, ensure "Append to existing values" is set to No.

Now create a SPD workflow on this List and try to access the column value (just log this value to the workflow history list). When you create an item and put some value to this column, you can see the workflow history displaying the correct value.

Now the not-so-cool part: Go to column settings, and change "Append to existing values" to Yes. Add a new item to the List. Go to the workflow history. Alas! The value is blank! In the SPD workflow, whether you set return value as "String" or "Plain Text", it always return blank!

Summary: If you are dependent on the value of Multiple Lines of Text column in SPD workflow, ensure you have not set "Append to existing values" to Yes.

Comments

  1. It only works if the Multi lines text field contains below 255 chars

    ReplyDelete
    Replies
    1. Thanks Maria for sharing your findings. Indeed, a strange behavior or bug!

      Delete
  2. Replies
    1. @Jegan, what's not working? Can you elaborate?

      Delete

Post a Comment

Popular posts from this blog

How to get SharePoint List or Library GUID via REST

Sometimes, you would need List or Library GUID to use that in some operation. In such cases, how do you get hold of GUID using REST API? There is a straight-forward end point which you can use: /_api/web/lists/getByTitle('ListTitle')/Id This will return the GUID of a List or Library. There is also another approach. However this approach works only if a List or Library contains at least one item. /_api/web/lists/getByTitle('ListTitle')/items This is a familiar end point which we use to fetch items of a List or Library. To get the GUID from the response, you would do: var listIDTemp = response.data.d.results[0].__metadata.id; var listID = listIDTemp.substring(listIDTemp.lastIndexOf("guid") + 5).split('\'')[0]; As you can see, we are doing string operations to fetch GUID from metadata.id. This contains information only if the response has at least one item.

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. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "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 peop

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. List of View Styles 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