I'm currently using Umbraco 10.7, I have an issue with the default length of dictionary item which only accept 1000 characters and I want to extend the limit.
According to this forum post (https://our.umbraco.com/forum/core/general/6898-Length-of-dictionary-item#comment-25272), I have tried updating the cmsLanguageText table manually from the database and change the datatype of Value column to nvarchar(max), but I'm still getting the character limit warning. I'm not sure if this approach is still valid with Umbraco 10 as the post was discussed 13 years ago.
Is there any work around with this? Also, if updating the database (probably with extra steps from the solution above) works, and if I were to upgrade the Umbraco in the future, will it revert the changes that I've made and possibly truncated the dictionary text which will cause data loss?
There is also a matching max length set in the view which is most likely why you are still seeing the warning.
I have a similar issue with the length at the moment too but am reluctant to change it for similar reasons in case it results in data loss in the future.
Edit length of dictionary item in Umbraco 10.7.0
I'm currently using Umbraco 10.7, I have an issue with the default length of dictionary item which only accept 1000 characters and I want to extend the limit.
According to this forum post (https://our.umbraco.com/forum/core/general/6898-Length-of-dictionary-item#comment-25272), I have tried updating the cmsLanguageText table manually from the database and change the datatype of Value column to nvarchar(max), but I'm still getting the character limit warning. I'm not sure if this approach is still valid with Umbraco 10 as the post was discussed 13 years ago.
Is there any work around with this? Also, if updating the database (probably with extra steps from the solution above) works, and if I were to upgrade the Umbraco in the future, will it revert the changes that I've made and possibly truncated the dictionary text which will cause data loss?
Many thanks, Afif
There is also a matching max length set in the view which is most likely why you are still seeing the warning.
I have a similar issue with the length at the moment too but am reluctant to change it for similar reasons in case it results in data loss in the future.
is working on a reply...