Creating reports and dashboards | Stimulsoft community forum

Hello,
is any possibility to call content (expressions) of some StiText like a function from another StiText object? In our old reporting tool was this feature and it has been used often by developers....
Thank you.

Hello,

During report rendering exist two instance of each component (minimum two instance).
One instance - component in report template.
Second instance - component which created for rendered report.
During creation of second instance report engine calculate expressions and write it to second instance. When you write expression like this:
you call instances from report template which does not contain calculated values from expressions.

You can:
1. Instead of "{Text1.TextValue}" expression use the same expression as in Text1.Text property, or
2. Use variables: in this case you can calculate value in variable, and then use this variable in expressions.

Thank you.

Unfortunetly this is not usable for us...
When I have StiText with expression {Text1.Text} I see no result. Why is not able your expression evaluator to evaluate expression in Text1.Text and put it in result of StiText which is calling it? I think this is not in incompatibility with yours evaluation process. Our old reports (PowerBuilder DataWindow Reports) have a lot of text fields with expression calling another fields (in some case even in several nesting levels) and if we convert this fields expressions into Stimulsoft and replace field names with their expressions, result expressions are very huge and unreadable.
Thank you ...

Hello.

LukasT wrote:Unfortunetly this is not usable for us...
When I have StiText with expression {Text1.Text} I see no result. Why is not able your expression evaluator to evaluate expression in Text1.Text and put it in result of StiText which is calling it? I think this is not in incompatibility with yours evaluation process. Our old reports (PowerBuilder DataWindow Reports) have a lot of text fields with expression calling another fields (in some case even in several nesting levels) and if we convert this fields expressions into Stimulsoft and replace field names with their expressions, result expressions are very huge and unreadable.

Sometimes it's impossible to find out which Text1 value you need to get. So it seems that using Variables with Read Only property will be useful for you.

Thank you.

In this time it looks like I have found some solution using variables, so thank you for consultation

Hello,

Ok.
Let us know if you need any additional help.