Practical Limit for Description Content?
What is the practical limit for how much information you put into the Description field using the rich text editor? We've got some users who are trying to use this field to create complex content and I've noticed strange behaviour with the asset, and poor response times, as the Description content grows.
Is there a practical limit that you would recommend? Thanks, |
One answer
Hi,
There is no set limit, but the bigger it is the longer it takes update/display/download/etc. It is not meant to be a replacement for a Word document! For example do not paste a large image directly in, it should instead be an image that is stored in the asset and attached as an image in the description field. That way the data is compressed in the image and brought down to the browser only when changed. If put directly in the text editor then it get's expanded into a text format (i.e. binary encoded as ascii) so that it can be downloaded as text in an html. This would actually makes things even slower and larger than an image in the asset attached to the html. A one page display of stuff is what it is meant for. Anything larger than that should be a separate document itself in the asset. Rich |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.