Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Data Source Error Invalid Column Name

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?

  • Anonymous's avatar
    Anonymous
    4 years ago

    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....

3 Replies

  • 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.⚡

    • Anonymous's avatar
      Anonymous
      Not applicable

      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....

      • HashamNiaz's avatar
        HashamNiaz
        Icon for Solution Sage rankSolution Sage

        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