Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi, Community,
I got data from an Excel file placed in a SharePoint, and the result I need is to load it from the Power Query Editor to Pivot and create visuals. However, when I close and apply it, I have a failing message to Load it, stating, "OLE DB or ODBC error: [DataFormat.Error] Invalid cell value '#N/A'.. An unexpected exception occurred".
Looking at the Excel file, I identified several rows with the "#N/A" value in numerous columns (these values do not come from calculations.). In Transform, Any Column group, I used the functionally Replace Errors using Value "null" for the entire table, but it didn't work, and I'm not allowed to change the Excel file.
Obs.: this is my first time posting in the community, so my apologies if any information is missing. I'll be happy to provide it.
Solved! Go to Solution.
HI @juniorc,
The power query table does not support '#N/A' as null values. Current one data field except 'any' type only supports storing one data type.
If your fields include multiple types of values, they will show the error of 'not able to transform data into specific data types'.
I'd like to suggest you add a replace function to check all the data fields to replace the NA to null to prevent this issue.
Regards,
Xiaoxin Sheng
HI @juniorc,
The power query table does not support '#N/A' as null values. Current one data field except 'any' type only supports storing one data type.
If your fields include multiple types of values, they will show the error of 'not able to transform data into specific data types'.
I'd like to suggest you add a replace function to check all the data fields to replace the NA to null to prevent this issue.
Regards,
Xiaoxin Sheng
Hi
I got similar problem and it was critical to put replace errors step when column is still in "ANY" type - it stop working when I changed type to other one
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 59 | |
| 43 | |
| 42 | |
| 23 | |
| 17 |
| User | Count |
|---|---|
| 190 | |
| 122 | |
| 96 | |
| 66 | |
| 47 |