Issues with qlikview Store -> CSV files; doesn't permit edits with Excel

[richard_cioci]

Hi Everyone,

I have a qvw file which processes incoming data and transforms it somewhat to prepare it for an intermediate stage of a small number of unique and exact alterations by an analyst (we have overall data come in from a large source which smooths a lot of the data, but an internal data source allows us to add some granularity and correct some of the imperfections that result from the smoothing).

So unfortunately, the edits can not be made automatic and can not be incorporated into the Qlik scripting, it needs to be manual. As such, I have been export that specific facts table to the csv format to allow them to make their changes and save, and then allows another qvw to pull in that modified csv file.

The problem that I am facing is that when I modify a CSV file which has been exported from Qlik and then save it, it messes up the CSV format, so that when the csv is re-opened, it combines all columns into 1.

I.E.

Company   Date    Sales

A               40295    6

B               40295    9

C               40295    12

after any modification to a sales number, i.e. changing 6->5 for company A, and then saving it, re-opening it gives me this

CompanyDateSales

A402956

B402959

C4029512

If I try to edit and then do save-as, it says that some features are not compatible with csv formats, so it signals to me that something about the csv files that the QV store command creates, has some sort of issue.

Is there anything I should add to the command to fix this issue?

The command I use is:

Store Increment INTO '$(PathData)Thyrogen_TSA_Increment.csv' (txt);

Thanks for your help.

[sinanozdemir]

Hi Richard,

Can you change your Store command to the below to see if it solves your issue:

Store Increment Into $(PathDate)Thyrogen_TSA_Increment.csv(txt);

Thanks

[m_woolf]

Can you post a sample csv file?

[stigchel]

This is more of an excel question, then a qlikview one. Probably the delimiters for your excel are different like e.g. a ";" for field delimiter. I would say that a file save as (instead of save) from excel and choosing the csv format will prevent messing up the data. In the consequential qv load you can change with what delimters to load using the file load wizard

[Peter_Cammaert]

You cannot change this Excel behavior from inside QlikView (moreover, this is a QV forum, not an Excel forum)

What you can do is this: in Excel, create an empty WorkSheet and place your CSV-data using Data->From Text (in Excel 2010). This menu item will offer plenty of features to correctly interprete the csv layout.

The message about "some features not compatible with csv-format" is because upon initially importing your csv-data, Excel will convert it into internal Excel structures with formulas and data formatting, which are not compatible with the csv-format (which is pure text) The data may perfectly survive an export without any harm done. The message is just a warning that appears everytime you do a text export. Again this is typical Excel behavior.

Peter

[#6]

Hi Richard,

Change your Store command to the below:

Store Increment Into '$(PathDate)Thyrogen_TSA_Increment.csv'

(txt, delimiter is ',')

This should help.

Thanks

Rajdeep