Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
Thanks for looking at my post. We having power bi portal and few reports were working fine, but suddently some of the reports fallen apart. When i try to refresh manually in the desktop version i am getting the below error. The question is it was working fine for so long and what could be the reason for this error pleasE? and any fix please?
Thanks a lot
Solved! Go to Solution.
Hi. The error is here because there was a wrong manual entry data. If you check the message it's trying to convert 0054-23 to number. That's not a number. The best solution is talking with the people/users that entry data for the source to let them know there is wrong value on their data. Explain which table and column has the wrong value. If they just don't care and won't change it, you can replace those scenarios with empty or 0 depending the calculations of the data model and let them be aware of the change with an email (evidence that you have asked for the best way and they didn't but you need to go through this).
That should fix it again. Data entry can be the worst kind of errors that can break semantic models.
I hope that helps,
Happy to help!
Thanks a lot for your input. It seems wrong multiple entries and which is now fixed
Thanks again
Thanks a lot for your reply
Issue is that is not only one number throwing an error but when i fix that in SQL side, new similar number throwing same error
Thanks
That's bad. That's why the first and best solution is the source. The users loading the data. Only when you can't make them understand the importance of the data entry is when you need to start thinking about the approach like "when you find a - then 0". That rule should be autorized by the sponsor or final user of the report.
Regards
Happy to help!
Hi. The error is here because there was a wrong manual entry data. If you check the message it's trying to convert 0054-23 to number. That's not a number. The best solution is talking with the people/users that entry data for the source to let them know there is wrong value on their data. Explain which table and column has the wrong value. If they just don't care and won't change it, you can replace those scenarios with empty or 0 depending the calculations of the data model and let them be aware of the change with an email (evidence that you have asked for the best way and they didn't but you need to go through this).
That should fix it again. Data entry can be the worst kind of errors that can break semantic models.
I hope that helps,
Happy to help!
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!