Forum Discussion
Refreshes for Datasets containing Calculated Tables over Direct Query to AS started failing Mar 30th
Hello, a year later and I still see replies here. Sorry folks, I've got the official answer and this scenario is unsupported. Not sure if this can change in the future but for now you can't use it. Why was it working before? Total mystery.
AugustoChaves Thanks for the update. Can you please post the referencing information, that identifies the bug you reported (eg. last five digits of the ICM# or something like that)? This is probably something that customers may want to vote on, or revisit in the future. It would be helpful to get a jump-start on my own discussions about this with them some day.
The confusing documentation is something that bothers me about this. I think they did a halfhast job of the docs ... and it is possible that they were doing so deliberately (ie. leaving their options open to change the implementation at a later time). Another unfortunate thing is that we experience a difference between the service and the desktop. Even in the docs they differentiate behavior in the "Service", in comparison to the behavior in the desktop
"Calculated tables aren't supported in the ***Service*** using this feature..."
see:
It seems like a cruel joke it is to allow this stuff to work on the desktop, and allow developers to build a solution, only to find out that it fails when deployed to the service. I'm guessing that on the desktop the whole solution runs in the context of the user's credentials, so there is no complexity related to the security infrastructure of the service/dataset/gateways/etc.
Insofar as complexity goes, I suspect the refreshing of a calculated table for Direct-Query-to-AS suffers from security challenges during refresh operations (some part of the dataset refresh that needs to occur outside of the context of the end user's credentials).
On the desktop, when "msmdsrv" is running in under the user's credentials, the security challenges don't really apply. It is possible that the differences we see in the desktop model are actually intentional, and they allow some powerful & flexible features to exist in certain related Microsoft tools, eg. "Power Pivot" in Excel.
Just guessing
Hi, I only have the number of the support ticket that was opened last year, 2203310040005513. Unfortunately I don't have the ICM#.