Forum Discussion
New Tables/Columns in SSAS not Showing Up In Report Field Well
Anonymous Thanks for the help, I was able to resolve the issue and your response finally got something to click in my head.
I was thinking that since the report was using a live connection to SSAS that it should just see SSAS as it is right now, hence the name live :smileyfrustrated:
Even though the content pack had been personalized, the dataset still shows as a shared data set (globe icon) which I assumes links back to some type of metadata about the SSAS database.
What I did to fix the issue is to simply go to the content pack and publish an update. This fixed the issue. I don't know for sure but I'm guessing the content pack update updated the metadata that the personalized content pack is pointing to. Only the user of the personalized content pack needed the new tables/columns so updating the content pack was not at the top of my mind.
So where I went wrong in thinking was that because the content pack had been personalized, that updates I made to the content pack would not affect the personalized versions. This is unfortunately true for most parts of personalized content packs, but not for the datasets, well at least for live SSAS connections.
Thanks Again Eno1978, and I agree with you, content packs need a lot of work in terms of updates and enhancements to the service but for our circumstances, we need to use them at this time.
Anonymous Thanks for the help, I was able to resolve the issue and your response finally got something to click in my head.
I was thinking that since the report was using a live connection to SSAS that it should just see SSAS as it is right now, hence the name live :smileyfrustrated:
Even though the content pack had been personalized, the dataset still shows as a shared data set (globe icon) which I assumes links back to some type of metadata about the SSAS database.
What I did to fix the issue is to simply go to the content pack and publish an update. This fixed the issue. I don't know for sure but I'm guessing the content pack update updated the metadata that the personalized content pack is pointing to. Only the user of the personalized content pack needed the new tables/columns so updating the content pack was not at the top of my mind.
So where I went wrong in thinking was that because the content pack had been personalized, that updates I made to the content pack would not affect the personalized versions. This is unfortunately true for most parts of personalized content packs, but not for the datasets, well at least for live SSAS connections.
Thanks Again Eno1978, and I agree with you, content packs need a lot of work in terms of updates and enhancements to the service but for our circumstances, we need to use them at this time.
TravisKale Glad you got it sorted out! One other point, that you didn't make, but probably know at this point. Any change you make to the Content Pack Structure, won't automatically flow downstream - you have to manually update the Content Pack to "push" those changes to the end consumers. Then they have to deal with the "get new version", etc, etc.