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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
delgadomk
Regular Visitor

Error - DataFormat.Error: We couldn't convert to Number. Details J7510

Hi,

 

I keep receiving an error when I import my excel file into PowerBI Desktop.  I think what is happening is that in some of the fields, there is a comma.

For example, I have a column titled Procedure Code and typically Procedure codes are just all numbers like 99213 but there are occassions when a Procedure Code will contain a modifier and that modifier is identified after theProcedure Code and is separated with a comma: 99213,PRO or 99213,52,AS.  How can I get PowerBI Desktop to reverse the error and just import the data like it is in the excel file?

 

Thanks,

Kim

1 ACCEPTED SOLUTION

Thank you! I made the changes to the excel file first then made them again in the Desktop and it seems to have worked.

View solution in original post

22 REPLIES 22
Anonymous
Not applicable

Thanks that worked for me. In advanded editor when selecting Changed Type and finding the field NAMEID it showed 

... {"NAMEID", Int64.Type}, ....

 

Then I just changed it to

... {"NAMEID", type text}, ....

 

and it worked Smiley Happy

 

 

 

 

This works for me too! 

 

Thank you!

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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