Forum Discussion
Split Column function not creating the correct number of columns on refresh
Hi pAAmckelvey ,
You can try to split the column into rows, so that the number of rows will change with the number of tags, and there is no variable limit.
If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
WinnizIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Super UserHi pAAmckelvey
In your query, you need to manually change the split column step. Right now it will looks something like this
#"Split Column by Delimiter" = Table.SplitColumn(#"Changed Type", "Tags", Splitter.SplitTextByDelimiter(";", QuoteStyle.Csv), {"Tags.1", "Tags.2", "Tags.3"}),You can see that it has a list at the end {"Tags.1", "Tags.2", "Tags.3"} which means it will split the column into 3 columns with those new column names.
Delete that bit so the step looks like this
#"Split Column by Delimiter" = Table.SplitColumn(#"Changed Type", "Tags", Splitter.SplitTextByDelimiter(";", QuoteStyle.Csv))
and the query should now split the Tags column into as many columns as needed, regardless of how many tags are in the column.
Regards
Phil
This does not work, instead, the column is entirely removed since there are no defined headers
