i have a property which uses the tree multi picker with ultimate picker compatibility. i had originally used nvarchar which worked fine until the client added a product which needs many, many things added via this property.
there is a 'length of field' type error. i have tried just changing from nvarchar to ntext, but the tree then becomes unpopulated.
is there a way of increasing the length allowed for the nvarchar? i would prefer to change to ntext, but is there a way to do this which would not involve having to repopulate all the data?
[i have however managed to duplicate this post - i thought i had deleted this one and then started one in the tree multi picker general forum]
i did eventually find the content in that table and it crossed my mind, but i am nervous of the adverse efect it may have - [anyone??]
i came to the conclusion that i may be better scripting the data from one column to the other, then changing the data-type on the 'datatype'.
i would rather do this i think, but it would be nice for someone to confirm whether changing the length of the field would be ok, or whether it may result in disaster.
Should also work, checked the core code and don't see anything that would prevent you from doing so. But as said in your other post, updating the cmsPropertyData table (you could start by duplicating the content in both columns) seems a better solution.
Maybe an additional publish all for those nodes (altho don't think it's required as you're not modifying the doc type)
possible to increase elngth of nvarchar
hi
i have a site in v 4.5.2.
i have a property which uses the tree multi picker with ultimate picker compatibility. i had originally used nvarchar which worked fine until the client added a product which needs many, many things added via this property.
there is a 'length of field' type error. i have tried just changing from nvarchar to ntext, but the tree then becomes unpopulated.
is there a way of increasing the length allowed for the nvarchar? i would prefer to change to ntext, but is there a way to do this which would not involve having to repopulate all the data?
thanks
Hi,
Have you tried changing the length of the 'dataNvarchar' column in table cmsPropertyData from 500 to whatever suits your requirement?
Disclaimer: Haven't tested this and may cause other exceptions/errors!
Cheers,
/Dirk
i haven't, not yet
[i have however managed to duplicate this post - i thought i had deleted this one and then started one in the tree multi picker general forum]
i did eventually find the content in that table and it crossed my mind, but i am nervous of the adverse efect it may have - [anyone??]
i came to the conclusion that i may be better scripting the data from one column to the other, then changing the data-type on the 'datatype'.
i would rather do this i think, but it would be nice for someone to confirm whether changing the length of the field would be ok, or whether it may result in disaster.
thanks
Should also work, checked the core code and don't see anything that would prevent you from doing so. But as said in your other post, updating the cmsPropertyData table (you could start by duplicating the content in both columns) seems a better solution.
Maybe an additional publish all for those nodes (altho don't think it's required as you're not modifying the doc type)
Cheers,
/Dirk
thanks dirk.
fuller reply and results in the other post:
http://our.umbraco.org/projects/backoffice-extensions/tree-multi-picker/tree-multi-picker-general/13255-change-datatype-without-data-loss-is-this-possible?p=0#comment48834
is working on a reply...