-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Execute_mdx - Sandbox Dimension #789
Comments
I agree. We should introduce an optional argument to the |
For reference, when using |
Hi @sbethea-cw, can you confirm that fix #812 works for you?
|
Hi @MariusWirtz, I tested |
I have run into an issue when transferring data between two servers where tm1s.cfg parameter EnableSandboxDimension is different between the two servers. If EnableSandboxDimension=T on server1 and =F on server2, then the dimensionality of the cellset is not the same.
When I use execute_mdx on server1, the cellset looks like:
{('Base', 'ele1', 'ele2', 'ele3', 'Value'): 12345}
but server2 has EnableSandboxDimension=F and expects the cellset to look like:
{('ele1', 'ele2', 'ele3', 'Value'): 12345}
TM1 throws an error saying 'Base' is not a valid element, like this:
Error: Prolog procedure line (3): Invalid key: Dimension Name: "Version", Element Name (Key): "Base"
Can a feature be added to execute_mdx to exclude the sandbox dimension if it is turned on?
The text was updated successfully, but these errors were encountered: