"branching issue when updating from version 6.x to 7.2"

kayman

Using RM7.2 below works :

 

<operator activated="true" class="branch" compatibility="6.4.000" expanded="true" height="82" name="something" width="90" x="45" y="30">
<parameter key="condition_type" value="expression"/>
<parameter key="condition_value" value="equals(&quot;%{myMacro}&quot;,&quot;1&quot;)"/>
<parameter key="expression" value="equals(&quot;%{myMacro}&quot;,&quot;1&quot;)"/>

....

but when upgrading the operator to 7.2 it fails (using else instead of if as to be expected) (as below)

 

<operator activated="true" class="branch" compatibility="7.2.000" expanded="true" height="82" name="something" width="90" x="45" y="30">
<parameter key="condition_type" value="expression"/>
<parameter key="condition_value" value="equals(&quot;%{myMacro}&quot;,&quot;1&quot;)"/>
<parameter key="expression" value="equals(&quot;%{myMacro}&quot;,&quot;1&quot;)"/>

 

So, is there a change in how macro values are to be called between v6.2 and v7.2?

bhupendra_patil

6.5 intridocued the eval function for handling macros

here is an excerpt from 

 

http://docs.rapidminer.com/studio/releases/6.5/

 

The macro expression %{} is now a regular function, evaluated just as any other function, and results in the string value of the macro. The new eval("expression") function allows you to evaluate strings as expressions. To resolve the value of a macro (i.e., as a number), use eval(%{macro}). If a macro references an attribute by name, treat it as an expression written as eval(%{macro}) or the shorthand #{macro}. (This shorthand is only applicable for attribute names.)

 

Also i tried updating XML and it seems to wrok fine, you need the hit the checkbox dialog, if the edited xml has issues then may be it may not update