Forum Discussion

trevb's avatar
trevb
Icon for Advocate II rankAdvocate II
10 years ago

Object reference not set to an instance of an object

So I have my PowerQuery working perfectly but when I apply and load the "Apply Query Changes" comes back with the error above.  I'm not sure what is causing this but I may have a suspicion.  My query...
Need Help
DataGuy2016's avatar
DataGuy2016
Icon for Advocate IV rankAdvocate IV
9 years ago

This appears as a bug in the desktop release Version: 2.43.4647.541 64-bit (February 2017)

igaca's avatar
igaca
Icon for Helper III rankHelper III
9 years ago

Having the same issue; cannot model anything (get the error when connecting fields to establish relationships).

 

I skipped the January version due to all the issues folks were reporting, now would like to revert back to December - does anyone have available to share?

 

 

  • Anonymous's avatar
    Anonymous
    Not applicable
    9 years ago

    Hi, It took me a couple of hours to figure why Power BI wasn't creating the relationships out.

    Error message was:

    "Unexpected error Object Reference not set to an instance of an object". (Very informative)

    Checked the data was clean, trying different data sources that were working before, etc. Then I tried creating the relationship in the other direction and it worked without any issues XD.

    With that I mean when I drag and drop from Table A to Table B, the exception occurs; when I drag and drop from Table B to Table A, works.

     

    Hope this helps! 

     

    • Steve88's avatar
      Steve88
      Icon for Advocate I rankAdvocate I
      9 years ago

      Yeah, I found the same worked for me. Seems like an odd new feature.

    • MartinCarlsson's avatar
      MartinCarlsson
      New Member
      9 years ago

      Thanks - worked for me... you saved me hours :D

      • sguenther's avatar
        sguenther
        Icon for Advocate II rankAdvocate II
        9 years ago

        This problem still persists for me. Unfortunately it can not be solved by a change of relationship direction, since it only occurs when grouping rows in a table coming from the Google Analytics connector.

         

        I have this problem since the release of the April update. I'm currently still running the March version, since also the May update did not fix this obvious bug. Any help/fix is highly appreciated.