OpenLab manipulates the code irregularly and independently, when a aggregator is formed - OpenLab CDS 2.5 Reporting

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




Parents
  • Hello,

    What version of CDS 2.x are you using? Known types of reported RTE expression corruptions have been fixed across the IR version changes. The issue is typically in the conversion of the editor expressions to the actual expression in the RDL file snippet. If the issues you are seeing are reproducible, please report them to applicable support group. If you are a workstation customer, you would contact your regions support number or reporting process. Client server customers should have access to the informatics support portal for issues like this one.

    Marty

Reply
  • Hello,

    What version of CDS 2.x are you using? Known types of reported RTE expression corruptions have been fixed across the IR version changes. The issue is typically in the conversion of the editor expressions to the actual expression in the RDL file snippet. If the issues you are seeing are reproducible, please report them to applicable support group. If you are a workstation customer, you would contact your regions support number or reporting process. Client server customers should have access to the informatics support portal for issues like this one.

    Marty

Children
Was this helpful?