Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
I'm connecting to an Azure SQL db. I haven't had a problem with other tables and views on this server, but for some reason, this view is giving me trouble. Any idea how to resolve this error?
DataSource.Error: Microsoft SQL: Invalid column name 'Exception'. Details: DataSourceKind=SQL DataSourcePath=....database.windows.net;OpsRpt-SQLDB-EUS Message=Invalid column name 'Exception'. ErrorCode=-2146232060 Number=207 Class=16
Is the problem with the actual column name 'Exception'? Is this a reserved word?
Solved! Go to Solution.
thanks for the reply parry. I ended up deleting the query, and starting again, and the view was just fine....not sure what was going on....
@Anonymous interesting, not sure. Can you create a view in the SQL and rename the column to something different and see if it works. Atleast that will give the clarification.
✨ Follow us on LinkedIn
Learn about conditional formatting at Microsoft Reactor
My latest blog post The Power of Using Calculation Groups with Inactive Relationships (Part 1) (perytus.com) I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop-shop for Power BI-related projects/training/consultancy.⚡
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
thanks for the reply parry. I ended up deleting the query, and starting again, and the view was just fine....not sure what was going on....
Hi @Anonymous !
It seems someone has renamed the column name which breaks your query since it might be using (select * from view) format to refer the view.
When you deleted the query & re-created it, it works fine because of the schema refresh.
Regards,
Hasham
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 65 | |
| 64 | |
| 49 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 119 | |
| 117 | |
| 38 | |
| 36 | |
| 29 |