Visuals Break with "Error Fetching Data" When Filtering by Date (Import Mode Model)

[Ahmad_1]

Hi everyone,

I’m facing an issue in Power BI where visuals break and display an “Error fetching data for this visual – An unexpected error occurred” message whenever I try to apply a date filter (as shown in the attached screenshot).

Here are the key details:

• The data model is in Import mode.

• The error appears specifically when filtering data on TransactionDate (or any date column).

• The visuals work fine before applying the date filter.

• I’ve already tried refreshing the dataset and rebuilding the visual, but the issue persists.

Has anyone else experienced this issue or found a solution/workaround for it?

Any guidance would be appreciated.

Thank you!

[v-kpoloju-msft]

Hi @Ahmad_1,

Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to @BeaBF, for his inputs on this thread.

The error “Error fetching data for this visual an unexpected error occurred” typically appears when the report encounters an issue processing date filters in Import mode.

A few users have reported similar behaviour, especially when using date slicers in “Between” mode. Please try the following steps:

Change the slicer type from Between to Before, After, or Relative date. Recreate the affected visual and test again. Clear the cache (File > Options and settings > Options > Data Load > Clear cache) and restart Power BI Desktop. Test in an earlier or 64-bit version of Power BI Desktop, as some recent builds have shown similar behaviour.

Also, refer those solved links:
1. https://community.fabric.microsoft.com/t5/Desktop/An-unexpected-error-occurred-file-quot-line-functi... 
2. https://community.fabric.microsoft.com/t5/Issues/Error-fetching-data-for-this-visual-An-unexpected-e... 

Hope this helps. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @Ahmad_1,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[v-kpoloju-msft]

Hi @Ahmad_1,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[Ahmad_1]

Hi @v-kpoloju-msft , 

Thank you for the support. I haven't tried the solution you provided yet. I just want to know one more thing: does it work well with Power BI Report Server?

[v-kpoloju-msft]

Hi @Ahmad_1,

Thank you for the follow-up. The steps we shared earlier were primarily tested for Power BI Desktop / Fabric. While some of the suggestions like changing slicer types or clearing cache can also apply to Power BI Report Server, we haven’t seen official confirmation that the exact fix fully resolves this issue on Report Server builds.

I would recommend testing the steps first in a safe report copy on your Report Server environment. If the issue persists there, we can help investigate further and check if any Report Server-specific considerations are needed.

Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you.

[v-kpoloju-msft]

Hi @Ahmad_1,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[Ahmad_1]

Hi @v-kpoloju-msft ,

Apologies for the delay. Yes, it works completely fine after downgrading the Power BI Report Server from May 2025 to January 2025. However, I’m facing another issue when I upload my report (PBIX file) to the Report Server and try to add my data source credentials for setting up the refresh schedule, it gives me the following error:

"Couldn't connect The report server couldn't connect to the data source using the information you entered. Make sure you've entered the connection string and any credentials correctly. Hide error details Requested value 'None' was not found."

Although it works fine in Power BI Desktop 2025 (Optimized for Report Server). 

[v-kpoloju-msft]

Hi @Ahmad_1,

Thanks for confirming that downgrading to the January 2025 Report Server resolved your earlier issue glad to hear that.

Regarding the new error: "Requested value 'None' was not found"

This usually appears when the authentication type or credential settings in the Report Server don’t match those used in Power BI Desktop (Optimized for Report Server). Please check.

The data source type (e.g., SQL Server, Analysis Services, etc.). The authentication method selected in Report Manager. That your PBIX was saved using Power BI Desktop (Optimized for Report Server – January 2025).

You can also try deleting and re-adding the data source connection in Report Manager, then restarting the Report Server service. If the issue persists, please share the above details so we can help identify whether it’s a credential or version-related issue.

Thanks again for your patience and detailed follow-up.

[Ahmad_1]

@v-kpoloju-msft, I'm using a MySQL database, and in Power BI Desktop (Optimized for Report Server), it works completely fine. Moreover, I installed the MySQL Connector compatible with this version of Power BI (Optimized for Report Server).

There's no issue with the credentials. I'm using the same credentials in MySQL Workbench, and it works fine.

[v-kpoloju-msft · Accepted solution]

Hi @Ahmad_1,
Thank you for the Follow-up question and confirming that the credentials and MySQL Connector are working fine in Power BI Desktop. 

Based on your setup (MySQL Connector/NET 8.3.x with Power BI Report Server January 2025), this error can occur if the connector isn’t correctly registered or accessible to the Report Server service. Please try reinstalling the connector using Run as Administrator so it registers properly in the Global Assembly Cache (GAC), then restart the Power BI Report Server service. Also, ensure the Report Server service account has read access to the connector’s installation path.

If the issue persists, try using the previous stable MySQL Connector version (8.2.x), which has shown better compatibility with the January 2025 build. After reinstalling, re-upload the PBIX and re-enter the credentials in Report Manager.

Let us know how it goes we will be happy to assist further if the error remains.
Thank yor for using the Microsoft Fabric Comminity Forum.

[Ahmad_1]

Hi @v-kpoloju-msft ,

Thank you for your support. After downgrading the MySQL Connector version from 9.5 to 8.2.0, everything is working perfectly. My report is now refreshing successfully, and I’m no longer facing any connectivity issues.

[BeaBF]

@Ahmad_1 Hi! Try these tests:

1. Check for Relationship or Model Corruption

Sometimes a corrupted relationship or inactive date relationship causes visuals to break when date filters are applied.

Try this:

• Open Model view and check if your TransactionDate column is properly related to your Date table (if one exists).

• Temporarily remove the relationship and re-add it.

• If you’re using multiple date columns, ensure only one active relationship exists between tables.

---

2. Validate Data Type and Format

If TransactionDate isn’t consistently recognized as a Date/Time type (for example, text or mixed types), Power BI’s internal engine can fail on filtering.

Check:

• In Power Query → Confirm TransactionDate is set to Date (not Text or Date/Time).

• Ensure there are no null or invalid date values after type conversion.

---

3. Test the Filter in Data View

Try applying the same filter in Data view (not Report view) to see if it triggers an error.
If it does, the problem is in the data itself (e.g., invalid date conversions or blank values).

BBF

💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!

[Ahmad_1]

Hi @BeaBF,

Thanks for your prompt response.
I've tried all the suggestions you provided earlier, but it still doesn't work.

• All my relationships are active.

• The TransactionDate column is in Date format.

• I don’t have a dedicated Date table.

[BeaBF]

@Ahmad_1 the issue occurs only when filtering by date, the missing dedicated Date table is now the most likely root cause.

Try these steps:

• Create a Date Table (DAX):
  In Modeling → New Table, paste this:

  DateTable = ADDCOLUMNS ( CALENDAR (DATE(2015,1,1), DATE(2030,12,31)), "Year", YEAR([Date]), "Month", FORMAT([Date], "MMM"), "MonthNumber", MONTH([Date]), "Quarter", "Q" & FORMAT([Date], "0#") )

• Mark it as a Date Table:

  • Select DateTable in the Fields pane.

  • Go to Table tools → Mark as Date Table → Choose the Date column.

• Create a Relationship:

  • Connect DateTable[Date] → YourTable[TransactionDate] (single direction, active).

• Use the DateTable in Visuals:

  • Replace TransactionDate from your fact table with DateTable[Date] (or its hierarchy) in visuals and filters.

BBF

💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!

[Ahmad_1]

@BeaBF, I have tried the suggested solution, but it does not work.

[BeaBF]

@Ahmad_1 Hi! Can you share your pbix file? or try to explain how to reproduce the error?

BBF

💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!