We are using kendo react excel export in our project One of the header in grouped header column looks like "Arsenal & Arsenal". But when we export we are getting header as "Arsenal & Arsenal". "&" is replaced with "&" Is this the issue from telerik side?
Thank you
1 Answer, 1 is accepted
0
Konstantin Dikov
Telerik team
answered on 31 Jan 2022, 07:39 AM
Hi Krishna,
Thank you for contacting us.
Without a sample that replicates the issue, one thing that I could suggest is to try changing the font on PDF export as documented in the following help article:
Please give this a try and let us know if adding a font that supports unicode characters resolves the issue. If the problem persists, please try to isolate it in stackblitz, so we can debug it locally.
My question is for ExcelExport. We are using ExcelExport component from kendo-react-excel-export. Do you think the answer you suggested will work for Excel as well
Best Regards, Krishna
Konstantin Dikov
Telerik team
commented on 01 Feb 2022, 12:53 PM
Please excuse me for sending the wrong information.
In the context of excel export, the data that will be exported will be the data from the data items as is, which means that if you are storing the & symbol as "&", that`s what will be added to the exported file. With that in mind, you can replace "&" in the string value before passing the data.
If further assistance is needed, please isolate the issue is stackblitz, so we can test and debug it locally.
I am able to replicate issue. Here is the stackblitz link https://stackblitz.com/edit/react-ugsqbb?file=app/main.jsx
I have hard coded the "&" symbol and it's still exporting as "&"
Best Regards, Krishna
Konstantin Dikov
Telerik team
commented on 01 Feb 2022, 04:52 PM
Hello Krishna,
Thank you for creating an example demonstrating the issue.
After long debugging and going through the source code I have noticed that the issue is with compiling of the templates, which encodes special characters. I will have to discuss this further with the developers team, but for now you can try the following workaround, where the cells value is manually changed before saving: