Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
Thomas_Rieck_MW
Partner - Contributor II
Partner - Contributor II

Automation doesn't create a csv-file

I am trying to use Qlik automation to check whether a CSV file exists in a specific space and folder.If the file does not exist, the automation should create one with specific content. For some reason, this automation does not create a CSV file even though it should—the file is not where it is expected to be.

Does anyone have any idea why this is happening?

 

This is the entire workflow :

Thomas_Rieck_MW_2-1762264762191.png

 

 

List Data Files From Space:

It should just search for a certain file in folder “Audit”.

Thomas_Rieck_MW_3-1762264762196.png

If condition block :

Checks just if the filelist is empty …

Thomas_Rieck_MW_4-1762264762198.png

 

 

The variable blocks are just giving me a Textstring saying file found or file not found.

The vairiable block myRows (list):

Prepares some data for the csv fiole that should be created if its not already there.

Thomas_Rieck_MW_5-1762264762200.png

 

 

Create Data File in Space:

This block creates the file in a specific folder …

Thomas_Rieck_MW_6-1762264762203.png

 

 

 

 

Labels (2)
1 Reply
nevopotokcloudinary

Likely your flow is running, but the CSV never gets written because of how the last block is configured.

A few things to double-check:

  • In Create data file in space, make sure you’ve set:

    • the correct space and folder path (e.g. Audit/filename.csv, not just the space), and

    • file content to an actual CSV string (often built by looping over myRows and joining with line breaks). (Qlik Community)

  • Confirm the If condition really detects “file not found” (i.e. you’re testing for an empty list, not for null or some other value). (Qlik Community)

  • Check the automation run log – if the last block errors (bad path, no content, wrong space), the run will show as succeeded but the file step may be skipped.

If those three look good, try simplifying the flow to just “Create data file in space” with a hard-coded CSV string and see if that shows up in the expected folder – then plug your dynamic myRows content back in.