Remove the 255 character restriction on Hyperlink fields
There is currently a 255 character restriction on Hyperlink fields. This restriction impedes ability to save Urls that might include hash values are long query strings. Some examples where this is really common are links to SSRS reports (with parameters) and Search urls that contain refinements.
Thanks for your suggestions. We agree this can be a little restrictive and we’re going to look into it.
David Ferraro commented
Add another ridiculous limitation of the modern site. My list is getting long now. I tell my friends at other companies to avoid SharePoint if possible.
SharePoint replied that they are going to look at it back in March 2016 i.e. 4 year 9 months ago. And we are still awaiting the feature. Wow..
Vicky Chapman commented
Removing this restriction would mean you could directly link to other files within Sharepoint. The interactivity between related files would be amazing - imagine being able to click through from one file or folder to another.
This is a massive problem. Looks like this has been opened for some time now Sharepoint Team. Any update?
Marc Vranken commented
We use lists in the follow up of agenda items. When you want to copy the link of a one note page to a hyperlink field in a list it isn't possible.
Very disturbing ...
El Cidius commented
In my SPO, I am using the url to filter the documents libraries and try to reproduce the missing SPO2013 filter web parts. Unfortunatly, this limitation don't allow me filtering as I would like....
I don't understand why 5 years later this still is a problem.
It's a Microsoft Teams Live event that is generating a "too long" URL (277 vs. the acceptable 255), and it is a Microsoft product, SharePoint, that won't accept it. Why cannot Microsoft accept its own links? That seems crazy to me. Why doesn't Microsoft want its products to play nicely together?
James Norberto commented
Just an FYI: I found a workaround which worked on a test basis. I took the long url and converted to a MUCH shorter url via bit.ly. Of coursed it worked for a single possible event attendee — no idea how it would worked with events featuring upto 2000 attendees.
Also, the created page is only a secondary entry point to my regional events. The embedded hyperlink within an Outlook invite will always be my primAry entry point for Americas events.
Marcelo Sauaf commented
yup this is indeed a MUST otherwise we're stuck in relying in external URL shortening providers like bit.ly (that in certain cases, alas, we're not allowed to use due to security matters)
Mar 11, 2016 Admin - "We're going to look into it"...
Today if a user copies a url from the browser it includes all the view IDs which can easily get you over the 255 limit. This should be a setting to allow as many characters as we need
Going to add to this, basically everything in Teams (meetings, conversations, items in a list, etc.) are all over 255 characters, makes to really hard to reference them in a List.
Has to be addressed!
Just running across this tonight, trying to paste in a Teams Live link into a list....too long....
Now I'll have to use bit.ly or something to shrink it. Seems counterproductive.
Thinking about updating a database field for 4.5 years... really? 255 is way to short even for your OWN meeting products.
Trying to add Teams Live links that are way more than 255! Ugh Makes it difficult
How much longer will you guys be "thinking about it"?
Change it already, on ALL MS applications. This is increasingly becoming a problem for me in my Fortune 100 organization.
Four years to look into it...c'mon man.
Pretty much any teams generated link for our organization exceeds 400 characters. The multi line text field work around is useless as it has its own limitations - like not being able to be filtered.
It’s also not possible to use the link for your MS Teams live event audience. These links are always approx 277 charterers...