SharePoint has a number of different field types that you can set, some of which, like Hyperlink fields, have two parts: a hyperlink; and a description. When editing through the SharePoint user interface, both parts of the field are displayed on the screen to make it clear what you are entering. Unfortunately the same cannot be said if you’re trying to update a hyperlink field from Flow or Logic Apps. In this blog post, we will look at the drawbacks of using Flow and Logic Apps to update a hyperlink field, and what we can do instead to achieve the desired outcome. For the purpose of this article, I will be using Flow, there are no differences to the implementation within Logic Apps.

Hyperlink Field in SharePoint

To start with, let’s look at exactly how a hyperlink field is rendered within SharePoint and how it behaves when it’s entered into a list. In my example, I have a list called user profiles which will have a title, and a hyperlink field called Blog site. When you open the edit form, you can clearly see that there are two elements to the hyperlink:

  • URL
  • Display text

When I manually add an item into the list, SharePoint will automatically combine both parts of the hyperlink to display something which is nice and friendly to the end user.

Creating from Flow

We know that creating the list item manually will give us the desired effect, but what happens if I want to automate the creation of those list items using Flow. For the purpose of this demo, I’m going to manually trigger the Flow with a Flow button, and as a result of the Flow I’m going to put an entry into my User Profiles list. When I select my Site and List using the “Create Item” SharePoint action, it will show me the title, and my blog site fields, but only gives me a single text box for the hyperlink. So, what do I put? Just the URL?

If I do only include the URL, I’m going to just see that in the hyperlink field:

When I first came across this, I thought I know how this works! I have to separate the URL and the Description using a comma! (,Website). Error: Invalid URI

I know, I need to separate the URL and Description with a comma and a space! (, Website). Error: Invalid URI

Ok, I can get this, I need to surround each part of the string with quotes, and then separate them with a comma and a space (“”,”Website”). Error: Invalid URI

Flow is slightly better at telling you that this is going to work than Logic Apps. Logic Apps will take the string, however your format it, and pass it into SharePoint, so you’ll end up with,Website as the hyperlink.

I even tried to create a JSON string in the format which I know SharePoint will take the URL, but that just failed completely and triggered my Catch scope.

So no matter how I format this string or no matter what cunning plan I can come up with, I’m not going to achieve a friendly hyperlink in this way.

Updating with the Desired Outcome

Luckily, or not depending on your point of view, the REST API is available for us to call and use for some of the more intricate field types. Whilst this isn’t the most straight forward way, and most citizen developers will probably run a mile when they see this solution, it does work quite well.

I’m going to keep my original “Create item” action, and I’m going to create a new step using the “Send an HTTP request to SharePoint” action. It is effectively going to perform an update on the list item in order to set the hyperlink field in the desired way.

The HTTP request is basically going to use the PATCH verb in order to tell the API that I want to perform an update against the list item which I’ve identified by taking the ID from the creation action and passed into this one. It is then a case of creating the body of the REST call to update the field that you want. The key mistakes that people usually make here are getting the first “type” wrong as this identifies the SharePoint entity type. If you’re ever in doubt, use your browser to initiate a REST call by creating this URL and pasting it into the address bar (just replace everything in bold with the relevant detail):


This will show the JSON body which is returned from your list, so then just perform a find for “ListItemEntityTypeFullName”, then copy the value between the tags into your REST call body.

The URL field is effectively a JSON array which allows you to specify the Url and Description, so again, just update the relevant parts with whatever you want in there. In my example I’ve used static data, however, you could use dynamic data, or expressions to create the content.

'__metadata': { 'type': 'SP.Data.UserProfilesListItem' },
'BlogSite': {
'__metadata': { 'type': 'SP.FieldUrlValue' },
'Description': 'Website (From REST)',
'Url': ''

So if I run my Flow again now, I now get the desired result:

So what does all of this mean?

I’m hoping that sooner, rather than later, the Flow user interface will be updated to be able to handle hyperlink fields, and other types like it. This will allow us to edit such fields without having to resort to the REST API. The good thing is that the HTTP call action allows us to easily use the SharePoint REST APIs without having to worry about getting tokens to authenticate. The upshot of this is that if you want to create a URL in a list, using Flow or Logic Apps, and have it displayed in a friendly way, then there’s a little more work which you need to do to make it possible.


Views: 7.61K  | Categories: Office 365, Power Automate
About The Author
  • Mark Jones says:

    Matt, this is a wonderful post. Thanks for sharing it.

  • Joel Rodrigues says:

    Great post Matt!

  • imademyac0unt says:

    Great post man!

    I am trying to do the same thing but with an extra catch.
    The URL I am trying to enter in the URL field of the hyperlink contains the ID of the list. Any idea on how do I push the ID in the URL?

  • bruce-deb.hawkes says:

    Thanks Matt – Great post.
    I’m almost there but getting an error which I am assuming is because the hyperlink column that I want to update is within a Document Set.
    The Flow creates the Doc Set using a [Send an HTTP request to SharePoint] Post action, which works well. I’ve then used a Parse JSON action to find the ID of this newly created Doc Set. And then following your steps above with another [Send an HTTP request to SharePoint] Paste action.

    My Uri syntax seems to be the problem:

    i.e. error message:
    “Invalid JSON. A token was not recognized in the JSON content.rnclientRequestId: f39be9b2-c47f-4511-a4b2-9ed81b82c04drnserviceRequestId: 536a699f-90d0-0000-5422-aeb7d7c8a2ad”,
    “source”: “https://xxxxxxxxxxxxxxxxx/_api/web/lists/getByTitle(‘Test%20Doc%20Set%20Library’)/items(37)”,

    Is there additional JSON syntax required in the Uri to populate the Display text of the Hyperlink column in a Doc Set?

    Appreciate any feedback you could provide.
    Thanks Debbie

  • Debbie says:

    Yippee โ€“ I got this to work, and now realise that the Uri code was actually correct. I just added a few spaces in my body text and put the brackets on separate lines and now all working well. I obviously need to learn a bit more on correct syntax formatting. Thanks & Hope you have a great week.