1

Topic: QlikView: Problems with UTF-8 at export

Faced one serious problem in QlikView.
At all I do not know, from what side to it to approach.
We have QV Server 11.20.12018.0409.10
In  by an individual SQL query without conversions the table is read.
It normally looks on the screen. But........
At export to Eksel/csv the same field value in . Lines irons not how in others.
Problem in conversions UTF-8. The Same word can be recoded on a miscellaneous.
See a picture. Ahead "the superfluous" character. It  without - outside characters.
Because of it there are violations in pivot tables since "one and too" value is bifurcated.
The problem arises spontaneously. And even in lines with numbers (- numerical number of the document).
What actions to undertake to avoid unequal string conversions?
: say that very rare error smile

2

Re: QlikView: Problems with UTF-8 at export

LSV;
Try a macro with explicit instructions that did not think, and preempted as UTF8, type ActiveDocument. GetSheetObject ("Tablitsa_so_sletevshej_CodePage").Export "C:\catalog_for_csv_from_QV\pivot.csv" ",", 65001, false

3

Re: QlikView: Problems with UTF-8 at export

Andy_OLAP wrote:

LSV;
Try a macro with explicit instructions that did not think, and preempted as UTF8, type ActiveDocument. GetSheetObject ("Tablitsa_so_sletevshej_CodePage").Export "C:\catalog_for_csv_from_QV\pivot.csv" ",", 65001, false

Also what now to everyone  a macro to cling?
And it is possible to specify not 65001?
How to specify win1251? At I rumple only a kirilitsa/Latin.

4

Re: QlikView: Problems with UTF-8 at export

LSV;
Well try to do on side SQL explicitly convert (nvarchar (xxx)...).
And in regional settings at itself not-junikodnyj language on any German, restart, then again on cyrillic, then again on restart.
Windows - it such...

5

Re: QlikView: Problems with UTF-8 at export

Andy_OLAP wrote:

LSV;
Well try to do on side SQL explicitly convert (nvarchar (xxx)...).

So the problem arises at 1 line from 1000.
Normally on the big samplings.

6

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

it is passed...
So the problem arises at 1 line from 1000.
Normally on the big samplings.

It is necessary to cut REPLACE ([Column], char (9), "), it tabulation in multiline fields in the reference manual at filling of the table of a DB which were too lazy to cut at saving in a long line...

7

Re: QlikView: Problems with UTF-8 at export

Andy_OLAP wrote:

it is passed...
It is necessary to cut REPLACE ([Column], char (9), "), it tabulation in multiline fields in the reference manual at filling of the table of a DB which were too lazy to cut at saving in a long line...

In the table unambiguously there are no tabulation. Otherwise they would be in all exported lines.
But a trouble only in 1 from 1000.

8

Re: QlikView: Problems with UTF-8 at export

//But a trouble only in 1 from 1000.
If to take identical field values. I.e. among 1000 identical values can be 1, 2 with the superfluous character ahead.
....

9

Re: QlikView: Problems with UTF-8 at export

LSV;
The colleague, deliver FAR Manager, open a file on F3, and then translate on F4 in mode HEX and look at the code of this character...

10

Re: QlikView: Problems with UTF-8 at export

LSV;
For some reason I think that you see Unicode U+0009 in the beginning of a line.

11

Re: QlikView: Problems with UTF-8 at export

Looked .
The "left" character such (hex):
EF BB BF

12

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

Looked .
The "left" character such (hex):
EF BB BF

Here advise to cut BOM the separate utility .

13

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

Looked .
The "left" character such (hex):
EF BB BF

Generally check in the initial text in columns on MSSQL presence of such branching codes as ASCII 192, any of them inside QV  in BF, and becomes further BOM th.

14

Re: QlikView: Problems with UTF-8 at export

Andy_OLAP wrote:

it is passed...
Here advise to cut BOM the separate utility .

it is ridiculous, but at me the utility corrected nothing.
I in shock.
Three bytes cannot delete!!!

15

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

it is passed...
Ridiculously, but at me the utility corrected nothing.
I in shock.
Three bytes cannot delete!!!

Try to specify for the loaded data explicit Collation

LOAD *;
SQL select column1;
column2 COLLATE Cyrillic_General_CI_AS
from DB.dbo. Table

When at loading characters out of standard Collation spoil - switching from Microsoft OLED DB Provider for a SQL Server on Native Client sometimes helps
At you in the table "curve" characters initially arrive, therefore through their wizard even it is visible .
It is possible to hang up a macro on event with explicit instructions 65001 as UTF-8 .

16

Re: QlikView: Problems with UTF-8 at export

Andy_OLAP wrote:

At you in the table "curve" characters initially arrive, therefore through their wizard even it is visible .

If to load a desktop (it at me 12.0), all APPRX.
And the server 11.20
Be primary cannot curves.
From 8 thousand lines only on one warehouse, the error in a warehouse title meets 4 times.
that if  cliques on this warehouse and to repeat outswapping, the problem DOES NOT APPEAR.
Real tin.....

17

Re: QlikView: Problems with UTF-8 at export

To read so:
Be primary the data cannot curves.

18

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

If to load a desktop (it at me 12.0), all APPRX.
From 8 thousand lines only on one warehouse, the error in a warehouse title meets 4 times.
that if  cliques on this warehouse and to repeat outswapping, the problem DOES NOT APPEAR.

The colleague, and can be QV as Rafik - completely is not guilty? I would run memtest for the sake of interest smile

19

Re: QlikView: Problems with UTF-8 at export

While the cat got out the self-made utility. Cleans  DOM.
One of real variants -  to 12.
Remaining yet did not help.

20

Re: QlikView: Problems with UTF-8 at export

LSV wrote:

While the cat got out the self-made utility. Cleans  DOM.
One of real variants -  to 12.
Remaining yet did not help.

Yes, at the people on QV11 SR3 the same nonsense with BOM.
And with the psychic too most.
[spoiler]
It not the bug, is a feature. "To cut, cut and once again to cut!" () V.I.Lenin, developer QlikView
[/spoiler]

21

Re: QlikView: Problems with UTF-8 at export

The important remark for those who will clean too this BOM:
Klikovsky CSV the file begins on BOM. And it it is not necessary to delete . On it the Ex-fur-tree understands that in file UTF-8.
It is necessary to delete all remaining entrances.