POWER BI, POWER QUERY ERROR: Requested value 'None' was not found

[Gammalt6]

Hi, I'm having this same problem with one of my BI's.

The file works well in my PC but when I share the file with one of my colegues, he has the same error = Requested value 'None' was not found.

I already tried to install different versions of OBDC connectors. I tried with 9.5, 9.4 and 9.3, reset the Power BI programm on the windows app settings, and deleted all the conection permissions and reconfigurer them. I don't have any steps in power query, its only the origin step.  What else should I try ?. I leaved the same version of OBDC that Its working on my machine in his PC. Another thing, the connection Its working fine on Excel so I'm assuming that Its something just with Power BI.

I have seen this publication, but nothing worked.

https://community.fabric.microsoft.com/t5/Desktop/Power-BI-refresh-Error-Requested-value-None-was-no...

[Jaywant-Thorat]

This “Requested value 'None' was not found” error is a known Power BI Desktop + ODBC edge-case, and the reason it works on your PC but not your colleague’s is not the connector version itself.

Let’s go step by step and cut through the noise.

-> What this error actually means (important)?

This error does NOT mean:

• ODBC driver missing
• Wrong driver version
• Bad credentials
• Broken query steps

It DOES mean:

• Power BI Desktop is trying to read a driver capability / metadata value from the ODBC driver and receives None, which Power BI does not handle gracefully.
• Excel and Power BI use different ODBC stacks → that’s why Excel works.

-> Why it works on YOUR machine but not HIS?
Power BI reads additional metadata that Excel does not, including:

• SQL dialect flags
• Parameter support
• Unicode handling
• Encryption defaults
• Driver capability enums

One of those returns None on your colleague’s PC.

This is caused by environment differences, not the .pbix.

-> The #1 root cause (90% of cases)
Power BI language / regional mismatch

On the failing PC:
Power BI Desktop → File → Options → Regional Settings

If:

• Language ≠ OS language
• Or decimal / list separators differ

Power BI mis-parses ODBC capability metadata → None error

-> Solution
Set everything to match Windows:

• Language: Default (Operating System)
• Regional format: Same as Windows
• Restart Power BI.

This alone fixes most cases.

=================================================================
Did I answer your question? Mark my post as a solution! This will help others on the forum!

Appreciate your Kudos!!

Jaywant Thorat | MCT | Data Analytics Coach
Linkedin: https://www.linkedin.com/in/jaywantthorat/
Join #MissionPowerBIBharat = https://shorturl.at/5ViW9
#MissionPowerBIBharat
LIVE with Jaywant Thorat from 10 Jan 2026
8 Days | 8 Sessions | 1 hr daily | 100% Free

[Gammalt6 · Accepted solution]

Hi, thanks to everyone.

I just solved the error, I was not using the ODBC connector, instead I was connected in my machine via MySQL directly, that was the error.

Greetings 

[v-echaithra]

Hi @Gammalt6 ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-echaithra]

Hi @Gammalt6 ,

I just wanted to check if the issue has been resolved on your end, or if you require any further assistance. Please feel free to let us know, we’re happy to help!

Thank you 
Chaithra E.

[cengizhanarslan]

This error usually isn’t “the driver version” — it’s Power BI failing to interpret a data source / credential / connector setting on your colleague’s machine (often because something in the connection is different even if the PBIX is the same).

The fastest things to check/fix:

1. Make sure they use the exact same connector in Power BI
If your source is ODBC, confirm the query is using the same DSN type:

• If you use a System DSN but they only have a User DSN (or none), the PBIX can open on your PC but fail on theirs.
  Fix: create the DSN on their PC with the same name, same driver, same server/db.

2. Check 32-bit vs 64-bit mismatch
Power BI Desktop is 64-bit for most installs. If their DSN/driver is 32-bit only, Excel might still work (depending on Excel bitness) while Power BI fails.
Fix: install the 64-bit ODBC driver and recreate DSN in ODBC Data Sources (64-bit).

3. Clear cached permissions + re-enter credentials
On their machine:

• File → Options and settings → Data source settings

• Remove the entries for this source

• Close Desktop

• Delete cache folder:

  • %LOCALAPPDATA%\Microsoft\Power BI Desktop\Cache

• Reopen PBIX and sign in / enter creds again

4. If using ODBC DSN-less connection, avoid “Driver={…}” differences
If your M has something like Odbc.DataSource("dsn=...") you’re fine.
If it has Driver={Some Driver Name}, that driver name must match exactly on their machine.
Fix: prefer a DSN, or edit the connection string to match their installed driver name.

5. Locale/Regional settings edge case
If the source returns values that depend on locale (dates/decimals) and Power BI parses differently, you can get odd enum errors like “None not found”.
Quick test: in Power Query, set Data type / locale explicitly for date/number columns (if you have steps). Since you say you only have “Source”, this is less likely.

[Murtaza_Ghafoor]

First, make sure Power BI Desktop and the ODBC driver are both 64-bit. If they don’t match, Power BI won’t recognize the driver. Recreate the ODBC connection using the correct ODBC administrator.

Next, delete the existing DSN on your colleague’s machine, restart the PC, and create the DSN again from scratch. Test the connection directly in ODBC, not only in Excel.

Then, confirm both machines are using the same Power BI Desktop version. It’s recommended to use the MSI installer instead of the Microsoft Store version.

After that, clear Power BI’s data source permissions and cache, restart Power BI, and reconnect.

Also, check that Windows regional settings (date and decimal format) are the same on both machines.

Finally, try a DSN-less ODBC connection. If that works, the issue is with the DSN configuration.

[tharunkumarRTK]

@Gammalt6 

Assuming the connection works correctly in Excel and the error occurs when loading the data from Power Query into Power BI, did you notice any differences in the M code generated in Excel versus Power BI? If so, could you try using the exact same M code in Power BI that works in Excel?

Connect on LinkedIn

Visit my website to read blogs on Power BI and Microsoft Fabric: https://www.techietips.co.in/

Did I answer your question? Mark my post as a solution!
If I helped you, click on the Thumbs Up to give Kudos. Proud to be a Super User!

[lbendlin]

Please provide more details. Show your Power Query code please.