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.
Denis S commented
Hi ! Maybe MS could develop a URL shortener, available within MS 365, instead of removing this limitation ?
There should be a workaround this restrictions. Does MS has a plan on reviewing this restriction ?
Bill Christie commented
This is impacting our Intranet when we attempt to link to OneDrive document locations. This suggestion has been in play for 6 years. Is it on the roadmap yet?
Bill Christie commented
This is impacting our ability to add links to OneNote on our Intranet. I would like to know if this will be addressed / is it on the roadmap?
It's really sad to see the MS tool which not able to process the links generated by other MS tools. I think this field type must be renamed into "Hyperlink (except MS generated)".
This is insane :D I start my first project with the new Microsoft Lists App and need to point to different files stored in SharePoint. But I can't, because the link is to long. The link, Microsoft creates is too long for a Microsoft tool...
I really try to avoid people from our org to use other tools, but so often, when I wanna convince them, that there might be a great alternative within the Office 365 Toolset, I figure out again... no: it's not better, it's not even usable for our scenario. Please, Microsoft, when you start so copy tools like Trello or Monday.com, make them better, not just look like the same but worse in use.
Harvinder Singh commented
I think Change in Site Settings : Site Features function will resolve this issue, activate following functions
Following Content, Metadata Navigation and Filtering,
Search Config Data Content Types,
Search Config Data Site Columns,
Search Config List Instance Feature, Search Config Template Feature,SharePoint Recommendations,SharePoint Viewers,Site Notebook,
Site Pages,Team Collaboration Lists,Workflows can use app permissions rest all I have deactivated and it worked for me
As I scroll through the Comments here it does not appear that anyone from the Sharepoint team is participating at all or even monitoring this issue.
That being Said, It would indicate to me that there is absolutely no Intent to Fix this or probably have completely given on addressing user issues with sharepoint.
Any Idea when this will be "Looked Into" and addressed? Its now been 5 FIVE years. And I cannot input links to documents people need, simply because the URL to the storage database to them is considered too long.
FYI I do not get to create the URL it is autogenerated.
Please fix this issue!
This is rediculous. Please increase the limit!
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.