Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Sudden SQL Error on DataSource refresh (CASE expressions)

Getting this error now when I went to refresh my datasource...

 

 

This is in a project that has been working fine. I went to add a field to the view that feeds this datasource. And that field was made up of a CASE statement with 3 levels. There are other small CASE statements in this view. The view runs fine in Sql Server Management Studio. I even tried removing the new CASE statements and still get the same error in Power BI. And this is using DirectQuery. Any thoughts of what is suddenly causing this?

Need Help

7 Replies

  • afreije's avatar
    afreije
    Frequent Visitor
    8 years ago

    I am getting the same on multiple reports of mine. Worked fine before the desktop update, and continues to refresh fine in the service (just not desktop version)

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      I just installed the latest update also a couple of days ago. This is the first change that I've had to make since installing the latest version.

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Another piece of the puzzle. When looking at the trace logs, it has the following error entries listed when I try to refresh the data source...

     

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    A co-worker of mine that has NOT updated to the latest version had no problem refreshing the data source and pulling in the new field, so it looks like in this latest build something broke. Here is what he is currently using...

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      So far, no. I submitted a support ticket and was told that this was a bug and would need to be corrected. I haven't been able to install any updates after November, 2017, as it was the December, 2017 release that introduced this bug. Wish I had more to tell you, but I haven't heard anything from the Power BI support team as to the status of this.

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Has this issue been fixed yet? It has a support ticket # 117121817339201.