EnableSandboxDimension parameter causing processes to fail

We identified a problem when we enabled the EnableSandboxDimension parameter in the tm1s.cfg file.

When we adjusted this parameter to true, we noticed that several of our processes began to fail, and upon further investigation, we discovered that the problem was caused by the inclusion of the sandbox dimension in the data source. For example, in a TI process that uses a two-dimensional cube as a source, we observed that the third column we accessed, which was supposed to represent the cube's value, had been changed by the sandbox value component, which is the base. It moves the value back one position and replaces it with "base".

Using ViewCreateByMDX with EnableSandboxDimension=T produces the following cellset: {('ele1', 'ele2', 'Base', 'Value'):12345}.
Having Base appear instead of cube value is problematic for us because we already have these variables declared in the processes we built. Turning on a configuration should not entail modifying all our TI procedures established over the years to cater for the inclusion of the sandbox dimension.

Request:
Add a parameter (e.g. <UseSandboxDimension>) to the ViewCreateByMDX function to include or exclude the sandbox dimension, i.e.

ViewCreateByMDX(Cube, ViewName, MDX_expression , <AsTemporary>, <UseSandboxDimension>);

Also, the <UseSandboxDimension> setting would ideally default to excluding the sandbox dimension when the TI process executes in the Metadata and Data section. The rational behind it is for backwards compatibility, i.e. existing processes can continue to function regardless of how the 'EnableSandboxDimension' is set in the tm1s.cfg file.

For clients, who find the SandboxDimension useful appearing in TI processes, they can set the <UseSandboxDimension> flag to yes.