At scale workaround - #40

Thank you for the contribution. Wouldn’t the following search by key instead of name? And what if an attribute has more than one key?

restrictions.Add(new AdomdRestriction(
                                "MEMBER_UNIQUE_NAME"
                                , args.LookIn + '.' + args.LookIn.Split('.')[1] + ".&[" + sLine.Trim() + "]"
                                ));

Can you share a screenshot of what args.LookIn looks like against AtScale? Trying to understand your logic for determining if we are connected to AtScale or not. Would there be some property of cmd.Connection which would tell you the server version or something that would say AtScale?

Let me muddle about how to test this.

Yes, by key instead of name and it wouldn't work for a composite key (just wouldn't find anything). That's why I suggested it's optimistic. I feel like this behavior might be suited for some sort of configuration option or checkbox as the original logic is superior (when all the restrictions are implemented).

As for what args.LookIn loks like, it looks like it would from any ssas cube, [dimension name].[attribute name]. The workaround is because AtScale hasn't implemented two restrictions that you use, so this is kind of a "best effort" for getting it to work with atscale.

I like the idea of detecting atscale connections somehow so it only runs the new code for those, I'll take a look at the command properties tomorrow and see if I can make a better if statement. I basically have no logic for determining we're in atscale right now, it just looks to see how many periods are in the lookin and if there's more than one, it just uses the original logic (cause the new logic didn't work for powerpivot models). But if I can detect AtScale somehow, I can easily isolate that code to only that scenario.

Alright, how about this? It only uses the AtScale code when UseAtScaleRestrictions is in the CustomData property of the connection? I couldn't find anything identifying it as an atscale instance so I think using CustomData may be the only option for us.

fixes #25