Thank you for getting back to us. We have managed to reproduce the problematic behavior and have logged it as a bug in our system. Please accept our apologies for the inconvenience caused, we'll be working on providing a fix for the upcoming releases. In the menatime, as a workaround I'd recommend you to add your custom field that will store the Description data (e.g. ListDescription) and hide the default Description field. You will be able to use your new custom field in the same ammner as witht he default one, you can represent the stored data by including:
Value='<%# Eval("ListDescription")%>' />
in your template. Once again thank you very much for the patience and kind cooperation in letting us know of this bug. Your Telerik points have been updated accordingly.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items