Solved

K2 List View Export to Excel feature

  • 2 December 2021
  • 9 replies
  • 49 views

Badge +2

Hi All,

 

The standard Excel Export from a K2 View escapes certain characters, e.g. & becomes & or becomes \.

Have you experienced this as well?

 

Version - 5.4

 

Regards

Zeeshan

icon

Best answer by ZeeshanNasim 9 December 2021, 16:25

View original

9 replies

Userlevel 3
Badge +11

Hi Zeeshan,


 


I'm not able to duplicate on my end with a test view. I assume that it is, but is your configuration the same as this explanation linked below?


 


Configuration Export to Excel 


 


Regards,


 


Jason

Badge +2

Hi Jason,


 


Yes the configuration is the same.


 


However I need to follow below code fix to get it work again :


 


https://community.nintex.com/t5/K2-Five-Cumulative-Updates-and/Code-Fix-Export-to-Excel-doesn-t-handle-multiple-spaces-or/ta-p/212670 


 


Regards


Zeeshan

Userlevel 3
Badge +11

Ahhh, ok. Yeah, I think that will solve the issue for you.


 


Feel free to mark your response as the solution if you'd like.


 


Jason

Hi Zeeshan


just FYI similar issue with '"' that is rendered as "


Our systems are on K2 5.5 FP7.


 


Not sure if the problem resurfaced, or it is new. 

Userlevel 5
Badge +13

I am also getting this issue on K2 5.5 FP5, and I don't see it mentioned in any subsequent fix packs. I think it has been re-introduced since it was fixed in FP3?

Userlevel 3
Badge +11

If you think this issue has been reintroduced in the latest fix pack, I suggest opening a ticket with  Nintex support so they can get a clear picture and log of what's happening. This will also help alert the dev team to the matter and help track the issue so it gets fixed and doesn't happen again.

Userlevel 5
Badge +13

Will do, I will report back here what is uncovered

Userlevel 5
Badge +13

It looks like the issue was addressed in K2 Five (5.5) November 21 Fix Pack 03, I didn't realize the fix pack numbering started over after a cumulative update comes out.

Userlevel 3
Badge +11
Thanks for the update!

Reply