Skip to main content
Nintex Community Menu Bar
Solved

K2 List View Export to Excel feature

  • December 2, 2021
  • 9 replies
  • 134 views

ZeeshanNasim
Forum|alt.badge.img+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

Best answer by ZeeshanNasim

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

9 replies

JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • December 9, 2021

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


ZeeshanNasim
Forum|alt.badge.img+2
  • Author
  • Rookie
  • Answer
  • December 9, 2021

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


JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • December 9, 2021

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


Forum|alt.badge.img+2
  • Rookie
  • January 4, 2022

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. 


Forum|alt.badge.img+15
  • Scholar
  • January 19, 2022

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?


JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • January 19, 2022

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.


Forum|alt.badge.img+15
  • Scholar
  • January 19, 2022

Will do, I will report back here what is uncovered


Forum|alt.badge.img+15
  • Scholar
  • January 20, 2022

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.


JRoberts
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • January 21, 2022
Thanks for the update!