Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hi,
So here's a breakdown of the situation, I am still rather new to PBI.
I have a dashboard along with its dataset in a workspace, and today when I tried to refresh the dataset, it failed without any error code (the dialog box is empty when I click on the (!) icon)
When I download the dashboard and open it with PBI Desktop, it tells me that a date field receives an invalid numeric representation (that's just a rough translation of the error message in french), and when I right click on the table that field is contained it and choose to edit the query, it opens up the results with no error, and when I go on to choose to refresh that table's data, the report works again, which is weird since when I choose to refresh the dataset from the PBI App, it still gives me an error.
Any idea what to do here ? It would help me out a lot.
Kindly,
Nossair
Solved! Go to Solution.
Hi @Anonymous ,
I have had this happen to me before as well. There is a difference between the way the Service and the Desktop run the code and every now and then the difference between the two cause an error to appear in one side while there is no error in the other side. The solution that has worked for me is to change the field (usually a date field) to a different type. And, then IN A SEPARATE STEP to change it back. Yeah, seems silly but that has worked for me. I think there is something in the background that gets "reset" when you do that. Let us know if that works!
I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
Proud to be a Datanaut!
Private message me for consulting or training needs.
Hi @Anonymous ,
I have had this happen to me before as well. There is a difference between the way the Service and the Desktop run the code and every now and then the difference between the two cause an error to appear in one side while there is no error in the other side. The solution that has worked for me is to change the field (usually a date field) to a different type. And, then IN A SEPARATE STEP to change it back. Yeah, seems silly but that has worked for me. I think there is something in the background that gets "reset" when you do that. Let us know if that works!
I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
Proud to be a Datanaut!
Private message me for consulting or training needs.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 10 | |
| 10 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 41 | |
| 36 | |
| 34 | |
| 28 | |
| 20 |