Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

SSAS report measure issue

I am connecting to a SSAS model with live connection, the report works fine. I can even add one or two report measures to the report and they also work fine. 

 

When I add a third measure an error box will appear with saying something went wrong: value cannot be null. Parameter name: key 

 

Has anyone experianced this error before and if so how did you fix it?

 

Thanks

Need Help

6 Replies

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      I am on 2.57.5068.501 64-bit (April 2018) I have seen other threads with the same error message, however they were all getting the error from other functions such as refreshing or opening a report. My report will open fine it is only when I add three or more report level measures do I get the error. I havent seen this exact issue in any other threads so that is why I opened this one.

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      v-xjiin-msft do you have any more information regarding this issue?

      • v-xjiin-msft's avatar
        v-xjiin-msft
        Solution Sage
        8 years ago

        Hi Anonymous,

         

        Since I can't repro your issue. I would suggest you to create a support ticket here to get more professional help.

         

         

        Thanks,

        Xi Jin.

  • rednuht's avatar
    rednuht
    Frequent Visitor
    8 years ago

    Getting exactly the same issue here, connected to Azure AS, we get this error when the third measure is created.

    • rednuht's avatar
      rednuht
      Frequent Visitor
      8 years ago

      Here's a simple workaround to avoid this error:

      Instead of clicking on "New measure" on the toolbar, just right-click on any table in the fields list and choose "New measure" from the dropdown menu.

      I've noticed that when the error occurs, the new measure is created without a home table, and is listed at the top of the fields list, this may be what's causing the error. With the workaround, it is created on whichever table the right-click was performed on.