Hi @Kofoworola George-Taylor,
Thank you for posting your question in the Microsoft Q&A forum.
According to your concern, this is an expected behavior of Power Query when you use Split Column by Delimiter. When using Split Column, Power Query generates an M step for example:
=Table.SplitColumn(Source, "YourColumn",Splitter.SplitTextByDelimiter(",", QuoteStyle.Csv),{"YourColumn.1","YourColumn.2","YourColumn.3"})
This will lock in the expected output schema, so if in the later refreshes you add more delimiters than the split step was built for, Power Query’s Table.SplitColumn M code will ignore extra split values. As expected, your FILTER spill and TEXTJOIN are working properly, but Power Query is still outputting only the original number of split columns and discarding any new parts beyond that.
To make a Dynamic Split step, you can try following the guidance with detailed explanation in this article: Split a Column Dynamically - Power Query - Tips & Tricks 6
(Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.)
I hope this information will help. If you have any questions or need further assistance, please feel free to reach out again on this post so I can continue to support you.
Thank you for your patience and understanding. Looking forward to your response.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.