The figure shows an MDX validation error. The syntax error message only indicates whether the syntax is valid or not. You must reexamine the MDX to find the error.
A common mistake when pasting MDX expressions from Microsoft Analysis Services is an ampersand (&) prefix on member names. Microsoft Analysis Services and Teradata BI Repository do not generate the same member unique names. MDX expressions from one system do not work verbatim in the other, particularly those using & prefixes on member names. The Teradata BI Repository syntax validator catches improper member unique names.
Validation checks the syntax of your MDX expression, but not the semantics. An MDX expression could thus pass the validation process, yet not function properly in BI client applications. It is helpful to pre-validate the MDX formula semantics using another tool. See the Excel error message for semantic errors in “The query did not run...” Message and MDX Issues, Functions and Operators.
To pre-validate MDX formula semantics, use a tool that connects through the ODBO interface specifically to Teradata OLAP Connector. Semantically test the MDX using the Teradata OLAP Connector provider’s actual characteristics straight to the data. Get ‘member unique names’ from this type of tool, as these vary by provider. For example, MDX Sample enables inspecting cube structure using Teradata OLAP Connector and seeing unique names. See MDX Validation Using MDX Sample. The Microsoft Analysis Services 2000 MDX Sample application allows you to test the expression.