back to forum.

Topic: Saving selected columns can be used for next iteration

Topic by
kanthuuuu

2012-02-29
12:24

Saving selected columns can be used for next iteration

Hi,

I need to save selected column parameters before exporting to CSV for next time just like as the database connection parameters when i run the tool next time.

It would be more helpful, if anybody can have a solution to achieve the task

Thanks in Advance

Reply by
kasper

2012-02-29
14:30
Hi there,

Not sure what you mean? Just like a database connection, DC stores all the information needed to read the CSV files. What information do you feel you have to re-enter?

Reply by
kanthuuuu

2012-03-01
08:38
Hi,
My intention is to the store the selected columns just like as database connection parameters (URL,User name and Password etc) when i re-use the tool

Eg: Suppose I have a XYZ Table with 5 columns

1. column 1
2. Column 2
3. Column 3
4. Column 4
5 Column 5

I always need 2 columns data(Column 1 and Column 4) as part of exporting to CSV. DC does not provides functionality to retain the previously selected TWO columns when i re start the program.

I need to retain two columns with status as checked when i re start the the tool

I am looking for functionality which is similar to Data base connection strings (URL. User name and Password) as part of connecting to the Database remotely. since they are storing in the user preferences dat file and can be retrieved by the tool when i restart the tool

Thanks in Advance

Reply by
kasper

2012-03-01
09:27
Sorry, I think I am completely not getting your point :) Here's what is stored about a CSV file in userpreferences:
  • filename
  • encoding
  • quote and separator char
  • header line number
  • whether to fail on inconsistencies or not

Just like a database connection, this is just enough information to derive the schema information when looking into the file (or database metadata). So in my opinion we save exactly the same amount of information about a CSV file as we do about a DB connection.

Every time the columns are discovered by DC, they are not stored. If it is a database, the columns are discovered through the metadata API, if it is a file, the columns are discovered by reading the header lines.

Sorry, but I am sure I am simply not getting your point :)

Reply by
kanthuuuu

2012-03-01
12:16
My Question here is how to store the previously selected columns using data cleaner tool. So that i can access the same for next time as part of exporting them to CSV.
Eg:
Suppose i have a schema called "student"
I have table called "student" on the schema "student"

suppose i selected Student Table on that i have five columns

name, address,class,marks and result

Always i need "name" and "marks" columns data only .

So i selected two columns "name" & "marks" and deselect the remaining columns and saved to the CSV File.

when i Restart the tool and follow the same steps like

selected the schema "student" and table "student" then its giving all 5 columns with status as "Checked"

My requirement is to get the previously selected columns "name" and "marks" as checked status instead of all columns before exporting the data to CSV File

Thanks in Advance

Reply by
kasper

2012-03-01
13:36
But isn't this just to save your job and then open your job (in the File menu) at a later time?

Reply by
kanthuuuu

2012-03-01
13:45
You r correct

could you please assist me how to proceed on this


Thanks in Advance

Reply by
kasper

2012-03-01
15:15
OK, once you've built your job, then instead of clicking "Run analysis", simply click "Save analysis job" (top left corner). Alternatively go to the file menu and select "File -> Save analysis job ...".

Once it is saved, you can reload it, again using the File menu: "File -> Open analysis job...".

Reply by
kanthuuuu

2012-03-02
07:42
Thanks a lot kasper

You need to be logged in to participate

In order to post your own comments on this topic, you need to be logged in.

Username:

Log in by clicking the login link at the top of the screen