Extract Model from Prod, added column, build, deploy, now users can connect to cube

  • I extracted the current model of a cube out of production, added a new new column to existing table with VS, and did a build, and deploy, and now users when they refresh an Excel, can get to the cube: error we couldn't get data from the external source. Here is the error message we got you: The CubeX cube either doesn't exist or has not been processed. I kept it the same name, and if I connect to it new via Excel I can see the cube and data. What can I do to rectify this problem?

  • quinn.jay - Thursday, March 2, 2017 2:52 PM

    I extracted the current model of a cube out of production, added a new new column to existing table with VS, and did a build, and deploy, and now users when they refresh an Excel, can get to the cube: error we couldn't get data from the external source. Here is the error message we got you: The CubeX cube either doesn't exist or has not been processed. I kept it the same name, and if I connect to it new via Excel I can see the cube and data. What can I do to rectify this problem?

    Is that the complete error message? Sometimes if you change the structure when you refresh in excel you get an error the first time. Simply refreshing again does the trick.
    If it's not that then check that the roles that were there previously are still there. Also check the connection string  of the  users' excel file.
    Finally, did the ID of the cube change? You said you "extracted" the cube model from production but you don't mention how. If you're not careful you can inadvertently change the ID of certain objects so roles and some connection strings will no longer be valid. I guessing you are an admin on the instance which is why you would be unaffected by any of the issues mentioned in this paragraph.


    I'm on LinkedIn

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply