Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Anonymous
Not applicable

Split causes errors

Hi,

 

Im having issues with with the split-function. Im splitting column A based on the first space:

 

#"Split Column by Delimiter1" = Table.SplitColumn(#"Added Custom", "Merged.1", Splitter.SplitTextByEachDelimiter({" "}, QuoteStyle.Csv, false), {"Merged.1.1", "Merged.1.2"}),

 

This however causes my numbers in column 11 to change to Errors, why is this and how to fix this?

5 REPLIES 5
dthompsonusa
New Member

Hello,

I'm having the same issue.  I am starting with a column that is Text type and splitting it on the ":"

dthompsonusa_0-1731686571606.png

The problem is the splitter creates the column with the numbers after the ":" with a type of "Number"  while it needs to be a type of "Text" thus causing an error.

 

Here is the splitter code:

= Table.SplitColumn(#"Changed Type1", "Product/Service full name", Splitter.SplitTextByEachDelimiter({":"}, QuoteStyle.None, false), {"Product/Service full name.1", "Product/Service full name.2"})

 

The value it is trying to split for this line is: Spiritless Inc:850018886208NR

 

Here is the result:

dthompsonusa_1-1731686725321.png

 

Your help is truly appreciated.

Thanks

For anyone following and having this issue I figured it out.  When the data first came into my power query the table set the format to text / number.  Note the ABC 123 next to "Column2" below.   I changed this to "text" so it showed "ABC" and then split the column.  The resulting 2 columns came through as type "Text" and the errors went away. 

 

Hope this helps!

dthompsonusa_2-1731689090622.png

 

az38
Community Champion
Community Champion

Hi @Anonymous 

Are you sure you need "QuoteStyle.Csv". it could be a reason, try to change to QuoteStyle.None for example

 

do not hesitate to give a kudo to useful posts and mark solutions as solution


do not hesitate to give a kudo to useful posts and mark solutions as solution
LinkedIn
Jimmy801
Community Champion
Community Champion

Hello

were you able to solve the problem with any reply given?

If so, please mark it as solution (to help other users find useful content and to acknowledge the work of users that helped you)
Kudoes are nice too

All the best

Jimmy

Jimmy801
Community Champion
Community Champion

Hello @Anonymous 

 

it could be that immediately after a TransformColumnTypes takes place and interpretes that data wrongly and therefore you get an error. 

Could you please post your M-code that is found in the advanced editor here? It should contain also a data example.

 

All the best

 

Jimmy

Helpful resources

Announcements
July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors