@DukoDragon
Yes, if the cell is null or empty, then there will not be anything there in the CSV. It will just have a delimiter, followed by another delimiter. In this case comma comma ( ,, ).
Are you saying this is causing other issues?
I did a test run with a comma-containing field, followed by a date field, followed by another comma containing field to replicate a piece of your data, but I didn't see any issues yet.
But judging from the expression you shared, it looks like that is one of the older versions of the flow. I don't recall anything that would cause what you may be describing in earlier versions, but you can try downloading Version 3 from the comment above or from the main post & try copying your flow into that new V3 template.
Unfortunately Power Automate does have a bug copying more complex expressions in actions through the clipboard, so I can't just give you individual actions to replace in your current flow. You actually have to copy everything else in your flow over to the new template.
Or maybe you just want your end result to show a null instead of blanks?
In that case you would need to use if( ) and empty( ) and null expressions to insert null if the field is empty & insert the value of it is not.
Hi @takolota
I am testing out the flow with a dataset that onlt hast the headers + 1line, but it has 34 columns.
The issue I'm having is that for some reason, most of the time it is duplicating the delimiter:
Now, if it was doing this consistantly I can just adjust and skip every other field, however the order changes using the same layout but with different data entered into the fields.
In one data set I get the "Tercera" result in one field, and in the other it moves down one:
Any ideas?
@Reinand
I tried recreating the data from the picture exactly and these were my results...
Other than the special Spanish characters, I'm not getting any errors. And I'm not getting any double delimiters. Could you share a screenshot of the Get file content or Set-up section so I can make sure there isn't anything weird happening with your CSV file or file type. Like is there already a second delimiter for each column in the data passed to the flow?
Because none of the column headers I saw even have commas in them, so most of the expression logic in the flow isn't even used or applied.
And it shouldn't matter for the error described, but are you working with the latest version 3 of the template?
Thanks,
Great, I'm glad we were able to identify the issue!
But it does seem like all of the links still download the previous version with the different expression in the "Select Reformat file data, replace in-data commas" starting from the 31st column.
Edit:
The issue on my end was that the ',' symbol to seperate 2 columns was duplicating to the end of one field and the beginning of the next (starting fro the second field).
I managed to fix this by simply adding a condition that if a field starts with a ',' to remove it, since it already shows up at the end of the previous field.
