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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
Suryamaxillian
Regular Visitor

Power BI refresh Error: Requested value 'None' was not found.

Requested value 'None' was not found.

Suryamaxillian_0-1762422689699.png

This error is showing while refreshing the data from MySQL in PowerBI. All the schema, table and column names are correct. It is happened after Navigation step in power query.

2 REPLIES 2
ANVS
Advocate I
Advocate I

Hello @Suryamaxillian 

The issue your facing is due to the SQL connector version mismatch between the Power BI SQL Connector and MySQL .NET Connector in your machine and also the metadata mismatch between Power Bi and Source.

 

Possible Solutions are like below:
- Check the MySQL Connector version between the two.
- Clear and Reconnect the Data Source

  • In Power BI Desktop, go to
    File → Options and settings → Data source settings → Clear Permissions,
    then reconnect to the MySQL source.

- Verify the Navigation steps:

 

  • Open Power Query Editor → Advanced Editor.

  • Check the Navigation step and remove any parameters or fields showing None.

- If the query still persists try the below:

Try disabling “Enable Native Database Queries” temporarily in Power Query.

😊 If this post helped you, feel free to give it some Kudos! 👍
And if it answered your question, please mark it as the accepted solution.

 

Mauro89
Resolver II
Resolver II

Hi @Suryamaxillian 

That “Requested value 'None' was not found” error usually appears when Power Query encounters a metadata or type mismatch — often introduced after a schema or driver change in MySQL.

Common causes might be:

  1. MySQL connector update or mismatch — sometimes the Power BI Desktop or Gateway driver version changes and the query references an outdated enum value.

  2. Changed data type or column metadata — if any column type changed (especially enum, set, or timestamp), the connector may fail to map it correctly.

  3. Navigation step caching — cached schema info from a previous session can cause this error after table renames or column changes.

Try these fixes

  1. Rebuild the navigation step:

    • In Power Query, delete or temporarily disable the Navigation step.

    • Reconnect to your table again via Home → Recent Sources → MySQL and navigate to the same table.

    • Compare the auto-generated query to ensure the schema matches.

  2. Update your MySQL connector:

    • Download the latest official MySQL .NET Connector (8.3+ recommended).

    • Restart Power BI Desktop afterward.

  3. Clear Power Query cache:

    • Go to File → Options → Data Load → Clear cache.

    • Reopen your file and refresh.

  4. Check special column types:

If your MySQL table includes enum or set fields, try casting them in SQL to varchar in a custom query:

SELECT CAST(enum_column AS CHAR) AS enum_column, ... FROM your_table;

Hope this helps you a bit.
 
Best regards!
 

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

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

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors