Type conversions (PEL)
The following table shows the implicit type conversions that the PerformancePoint Expression Language (PEL) compiler performs.
Type from
Type to
ConsolidationICMethod
Tuple
ConsolidationMethod
Tuple
ConsolidationUsePartnerEntity
Tuple
Hierarchy
MemberSet
Integer
Number
Level
MemberSet
Member
Tuple
Member
MemberSet
MemberSet
TupleSet
Model
Tuple
Null
Number
.gif "Note")
Note:
This conversion is direct. The conversion from Null to Number is never transitive through Member.
Null
Member
Note:
This conversion can be applied only when the declared constraint is a MemberSet.
Real
Number
Tuple
TupleSet
Tuple
Number
TupleSet
Scope
Remarks
A Tuple can be dereferenced to obtain a Number except in a Tuple specification.
A Hierarchy or Level type can be used where a MemberSet is required. The PEL compiler applies the Members (PEL) to the value, which returns a MemberSet.
Type conversions are applied transitively. That is, if Type1 can be converted to Type2, and Type2 can be converted to Type3, then Type1 can be converted to Type3. In the event that multiple options exist to convert from one type to another, the first applicable conversion has precedence at each step.
For example, a Member type can be converted to a TupleSet type in the following two ways.
From Member to Tuple to TupleSet
From Member to MemberSet to TupleSet
In this case, the PEL compiler uses the Member to Tuple to TupleSet sequence because Member to Tuple has precedence over Member to MemberSet.
A type can be upcast. For example, an Integer or a Real can be used wherever a Number is required, because an Integer or a Real is always a Number.