topic Re: Comma separator in number format missing when export to html in QlikView

Comma separator in number format missing when export to html

hectorvega — Fri, 09 Jan 2015 00:01:06 GMT

I hope some guru could help on this issue.

I am exporting a pivot table to html and sending it to an email. The formatting is loss but only the comma separator is missing.

Inspected the regional settings, the whole format on configuration and using also the num( expression, '#,###.##')

Nothing works.

Please help me to discover this is not a bug on QlikView.

Thank you!

Re: Comma separator in number format missing when export to html

Fri, 09 Jan 2015 00:08:20 GMT

User Preferences-> Export -> Number Formating

Re: Comma separator in number format missing when export to html

petter — Fri, 09 Jan 2015 00:10:28 GMT

Have a look at the User Preferences... Export / Default Export Options ....

Re: Comma separator in number format missing when export to html

hectorvega — Fri, 09 Jan 2015 00:14:01 GMT

Thank you for your response Mario,

But also this not work too.

Re: Comma separator in number format missing when export to html

Fri, 09 Jan 2015 00:15:27 GMT

Did you select Full Formatting in the Number Formatting option?.

Re: Comma separator in number format missing when export to html

hectorvega — Fri, 09 Jan 2015 00:27:41 GMT

Yes Mario. Full Formatting and and also did a num(expression,'$#,###.#') for each column on the pivot table.

I got a dollar sign on the exported html, but the comma is stripped.

Re: Comma separator in number format missing when export to html

hectorvega — Fri, 09 Jan 2015 01:27:22 GMT

Thank you Petter for your help.

But I did all the combinations and review also my regional settings and this is not working.

The comma is deleted as thousand separator.

Thx

Re: Comma separator in number format missing when export to html

Fri, 09 Jan 2015 02:52:26 GMT

attached a sample doc which I export to html, take a look at its default configuration. I'm not sure if I understood. Your issue is with the formatting itself right?. I could export the document along with the Sales column and it looks just like the Desktop's version.

Re: Comma separator in number format missing when export to html

Fri, 09 Jan 2015 02:55:21 GMT

I also tried with the Pivot version and it works, it keeps its original numeric format. I believe that If you make a test to export it manually from desktop as HTML and find that it looks good, then it is no the export step itself, it might bee the macro or program you are using that is sending it out along with the Email message.

Re: Comma separator in number format missing when export to html

hectorvega — Fri, 09 Jan 2015 20:17:51 GMT

Thank you for your nice responses.

The exporting test on the desktop works correctly, showing numbers with the comma separator as this example : $123,123.12

But running the VB Script macro with the following sentences :

SET objTable = ActiveDocument.GetSheetObject(ObjId)

objTable.ServerSideExportEx "C:\Aplicaciones\Reportes\OutPut\"& ResName &".html" , ";", 0

Shows the same number as $123123.12

The comma separator is missing.

The export preferences are correct as mentioned by Petter, The regional settings on the server for numerical data are correct.

Any Idea how to solve this?

Thank you very much for your time.

Re: Comma separator in number format missing when export to html

petter — Sun, 11 Jan 2015 11:25:04 GMT

I looked in to the QlikView API GUIDE documentation and I found actually not one but FOUR different API-calls which can export to HTML from a Macro VBscript (or JScript):

Client-side exports:

ExportHTML
ExportEx

Server-side exports:

ServerSideExportEx
ServerSideExport

The client-side exports actually behaves just like you expect - they are affected by the User Settings where you can switch on or off the thousand seperator on export.

The server-side calls does unfortunately not take this into consideration and will always export without the thousand seperator. The clue to why this is so is also to be found in the API Guide

Simplest and quickest solution:

Depending on how you need to design your solution you might be able to use the ExportEx but save the file to a server file-share which the necessary users that need to run the macro should have write-access to.

Another more elaborate solution that still use the ServerSideExportEx:

Abandoing the HTML as export option but saving it as text - but embedding the necessay HTML to actually get a resulting
HTML-file anyway and getting full control of any HTML - still keeping the thousands separator.

I have an example on how this can be done as a QVW if you want to investigate this solution. But it is more time-consuming and it is advisable to have HTML-development competence available...Depending on the setting it will be used it could be less dependable than

the #1 solution.

Conclusion:

The approach chosen depends a lot on the actual environment and the limitations posed by that. So knowing more about which client-side access will be used could be helpful to give further advice: Full Browser, IE Plug-In, QlikView Open-In-Server, tablets.... ?

How will mail be sent? From client-side or is it a server-side component/library? How will it be done? Interactively by the end-users or scheduled by QlikView Publisher or other scheduling mechanisms/products?