User Directory Connector via CSV File

[Anonymous]

Hi,

I'm creating an User directory Connector via Excel (ODBC).

I've installed the ODBC setup.

The csv files I'm using, are created via qlik sense like this:

user:

LOAD * INLINE [

    userid, name

    111, Marie

    222, Joanna

];

                Store  user into '$(vCSVPath)users.csv' ( txt, embedded labels, delimiter is ',', msq) ;

attributes:

LOAD * INLINE [

    userid, value,type

    111,email,  Marie@gggg.com

    222,email, Joanna@aaa.com

];

                Store  attributes into '$(vCSVPath)attributes.csv' ( txt, embedded labels, delimiter is ',', msq) ;

If I create a normal csv file outside qlik sense script and use this one, the UDC is created, but if I use the files generated through qlik sense script, it gives me this message:

And both files are exactly the same.

The only diference I can see is that the file generated by qlik sense script has a few more bytes (3),on file size.

Any thougths ?

Thanks in advance,

Sílvia

[kaushiknsolanki]

Hi,

I have came across the same situation. And the same procedure didn't work for me too.

The reason may be that the format in which qlik creates the csv is different from the csv's which are generated manually.

So we ended creating the manual csv's and txt file.

Regards,

Kaushik Solanki

[Anonymous]

Hi Kaushik,

Thanks for your answer, but for this app that is not a solution.

Because we're going to created this csv's files, reading data from a webservice.

It can not be done mannually.

Regards,

Sílvia

[daniel_dalnekoff]

Did you ever come up with a solution here?  I am stuck on the same challenge.  

[Øystein_Kolsrud]

Looks like Qlik Sense can only write CSV files using UTF-8, but the Excel ODBC driver can only read ansi. There's a thread on a workaround for the issue in QlikView here, but I'm not sure how applicable it will be for Qlik Sense: https://community.qlik.com/t5/QlikView-Scripting/Storing-txt-file-to-quot-UTF-8-without-BOM-quot/td-...

[Mauritz_SA]

Hi Silvia

Did you perhaps get a workaround for this? We are also stuck at getting our users from the external application into Qlik Sense. We can also expose and endpoint in the external application which can be consumed by a QS app, but we cannot store the information in a place/format where the Qlik UD connector can read it.

Regards,

Mauritz