Forum Discussion
Visuals Break with "Error Fetching Data" When Filtering by Date (Import Mode Model)
- 9 months ago
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! 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_110 months agoFrequent Visitor
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.
- BeaBF10 months agoSuper User
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!
-