Flexgrid export to Excel, currency and culture problem

Flexgrid export to Excel, currency and culture problem

Posted by: johan.holmstrom on 18 October 2020, 6:38 pm EST

• 

  johan.holmstrom

  • Post Options:
  • Link
    Copy

  Posted 18 October 2020, 6:38 pm EST

  Hello!
  
  I have implemented the FlexGridXlsxConverter to export data from some of my flexgrids. In the application we changed culture to swedish and therefore we get our currency as for example “1000 Kr” instead of “$1000”.

  It works fine in the application but when using FlexGridXlsxConverter the currency fields is shown as “Kr1000” for us. Does anybody have any ideas of how i can fix this?

  Thanks for your help!
  
  Sincerly Johan

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 20 October 2020, 12:21 am EST

  Hello Johan,

  We are sorry for the inconvenience caused. We were able to replicate the issue and have forwarded a bug report to the developers with internal tracking id 467457. We will update you once we will hear from them.

  Regards,
  
  Ashwin

• 

  johan.holmstrom

  • Post Options:
  • Link
    Copy

  Posted 20 October 2020, 10:26 pm EST

  Thank you very much Ashwin!

• 

  johan.holmstrom

  • Post Options:
  • Link
    Copy

  Posted 18 November 2020, 1:07 am EST

  Hi again. Have you been able to get a preliminary date when you think you can look into this? Is it a public issue id so i can follow it?

  Regards
  
  Johan

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 19 November 2020, 3:21 pm EST

  Hi Johan,

  Sorry but the issue is still with the developers. I have asked for an update on this.

  Is it a public issue id so i can follow it?

  The id is for internal purposes only and not publically accessible. We only add the id in the response so that any other engineer looking into your case can track the bug.

  ~regards

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 9 February 2021, 11:17 pm EST

  Hi Johan,

  You will be glad to know that the issue has been fixed in the latest nightly build of Wijmo. You can verify the same using the sample link below:

  https://stackblitz.com/edit/angular-1fdqzn-u5c3gl

  Note that nightly builds have not been passed through the QA cycles and are not suitable for the production environment.

  This fix will be included in the next stable build which may be released around April but I can’t provide an exact ETA right now.

  ~regards