Create CSV table Output empty

(0) Share

Report

Posted on by dev85

Hello guys

I'm building a CSV table from an Azure query, this is the flow:

when I tested the flow, I'm getting this results:

So, the Create CSV table it is reading fine the Query from devops(the input is right), however as you can see the Output just shows empty values.

I'm loading the Create CSV action like this:

One curious thing, at first in the create sharepoint file, I leave the file name with no .csv extension (I forgot) so when I run the flow it created a file with no extension, however when I renamed and add the .csv it worked and all the data from the query was in there perfectly, but when I add the .csv in the file name field in the Create File step, it just give me an empty table with just the column headers.

Any help would be appreciated.

All responses (3)

Answers (1)

czybach 2 on at

Like (0)

Report

Re: Create CSV table Output empty

Is there a solution for this that persists other than just having to rewrite all of the references every time you save the flow? I'm having the same issue, that every time I open the flow to edit it, the references revert from "." to "']?['" , which means every single time I have to service the flow I have to rewrite all of the dynamic content. How do I get it to not revert to the incorrect format?
dev85 44 on at

Like (0)

Report

Re: Create CSV table Output empty

Hi @Expiscornovus

Thank you so much. I didn't know how to correct the missing dot error and I just write the corrected expression in the column values and it worked perfectly.
Verified answer

Expiscornovus 32,140 Most Valuable Professional on at

Like (0)

Report
Re: Create CSV table Output empty

Hi @dev85,

Seems I can reproduce this issue. It looks like it turns the dot in the name of the field into two separate fields.

In my CSV table action I was using the following expression for WorkItemType:

item()?['System.WorkItemType']

When I reopen the flow in edit mode that got changed to:

item()?['System']?['WorkItemType']

That property does not exist and therefore it cannot find the values of it.

Here is an animation of the same behaviour.