[Bug-Report] Using XML in Custom Field

Hello,

Is it fine to use XML in Custom Field? When I typed in XML, then custom field shows weirdly in the dashboard when I tried to edit Custom Field.
Since then, Custom Field cannot be changed as it shows “Database error”

XML I typed is something like:

Please let me know if it is expected behavior/known limitation…

Seemingly the custom field can be retrieved correctly via LexActivator API.
So, I think it is just a small bug in Dashboard…

Custom fields are already structure with setter and getters on server and client side respectively. So, setting xml as a value is not intended.

Internally they are stored as an xml so storing an xml value will actually mess with the structure of the custom fields.

XML is convenient way to store the multiple data in single attribute for us as well…
Can you escape the problematic letters for custom field handling? Seemingly, double quotation (") is causing the problem in dashboard.

Thanks, will look into fixing it

Hi,

Issues is actually with the incorrect xml, it should be syntactically a correct xml. The allowed length of custom field name is 255, so your xml string got truncated making it invalid. Try using

Also using xml as custom field name doesn’t make much sense, as it is only accessible through the ID