Hi.
Currently, we retrieve the compound_name in our value expression via a custom calculation and use this as a condition in an if-then statement. That could be a text field or a table column. The resulting value is then passed on by creating a variable.
Now we noticed that OpenLab manipulates the code irregularly and independently when including a custom calculation in the expression and forming an aggregator or variable. This only becomes visible after saving the report template and reloading it.
For example, the expression "if(Compound_Name like CCR((Compound_CustomCalculationResults),"Compound_name_2"),[..]" suddenly becomes "if(Compound_Name like Compound_Name like CCR((Compound_CustomCalculationResults),"Compound_name_2"),[..]", which causes an error. "Compound_name_2" is a string. Is this an error on our part or is it a bug?
In addition, we could observe that one condition for custom calculations is duplicated as soon as an aggregator (and probably also a variable) is formed and several Custom Calculations are connected with "AND" or "OR". For example "CCR((Compound_CustomCalculationResults),"resolution_ep") >2 and CCR((Compound_CustomCalculationResults),"resolution_usp") >2" is converted to "CCR((Compound_CustomCalculationResults),"resolution_ep") >2 and CCR((Compound_CustomCalculationResults),"resolution_usp") >2 >2".
Thanks, Chris
