PEL-MDX feature comparison

The following lists compare features in Multidimensional Expressions (MDX) language and PerformancePoint Expression Language (PEL).

MDX features that are not supported by PEL:
- PEL does not support changing model metadata. For example, you cannot create, modify, or delete models, dimensions, hierarchies, or members.
- PEL does not support arbitrary SQL commands.
- PEL does not support MDX data-mining functions.
- PEL does not support the String-to-Tuple class of MDX commands. You cannot programmatically compose strings and have them interpreted as MDX commands.
- PEL does not support MDX optimization functions. The PEL compiler performs many of these optimizations automatically.
- PEL does not support Solve order.
- PEL does not support Pass order.
- PEL does not support referencing user-created member views in non-time dimensions.
PEL features that are not supported by MDX:
- PEL supports parameters in rules. The values of the parameters can be supplied at run time.
- PEL supports variables that represent model properties. Rules can use variables. The assigned value for a variable persists until it is explicitly changed.
- PEL provides explicit support for computations that are related to consolidation, currency conversion, intercompany reconciliation, shares and ownership values, and exchange-rate accounting.

See Also