We are currently using the Outsystems Data Grid and have encountered an issue. In our database, we have text entries that include the symbol ">". However, when displayed in the Data Grid, this symbol appears as "›". This discrepancy causes problems when we download the data as an Excel file and try to integrate it into another system.
We have tried to replace the symbol using the following action: Replace(ArrangeData.DataJSON,"›",">"), but nothing seems to work.
Has anyone else experienced this issue? Any suggestions on how to resolve it would be greatly appreciated.
Thank you!
Hi @Pauline Harlinghausen
Thanks for sharing since it allowed me to confirm what I thought was the "issue".
The reported use case happens because those characters will not be considered safe from a potential Cross-Site Scripting (XSS) attack perspective and, because of that, since the Grid configuration OptionalConfigs > SanitizeInputValues = true by default (following the security guidelines), all the JSON that will bind the Grid will be sanitized, so, in this particular case, there’s an encoding the Grid will interpret as ‹ or › instead of < or >
OptionalConfigs > SanitizeInputValues = true
‹
›
<
>
The information about the change on this default can be found on the release notes of version 2.17.0 and it’s quite clear:
So, if this is a requirement, you will need to assume this fact and set SanitizeInputValues=false and that way, the display, filters, and exports will work as expected:
SanitizeInputValues=false
SanitizeInputValues
See attached a modified oml with your use case before and after the change
Best Regards,GM
Thank you for the explanation that works!
Hi,
Replace(ArrangeData.DataJSON, "›", Chr(62))
Chr(62) represents the actual > symbol in ASCII.
This ensures that the character is correctly replaced before rendering in the Data Grid and before exporting to Excel.Thanks,sahana
Hello @Pauline Harlinghausen
To make collaboration more efficient, please share a sample oml with your use case so the community members don't need to invest extra time trying to replicate it.Also, what's the OutSystems Data Grid you're using?
Thank you for your efforts. Unfortunately, the first solution proposal did not work. Attached is the OML file related to the problem. We are using Outsystems Data Grid version 2.19.0.