Community
Participate
Working Groups
Created attachment 93958 [details] example test case +----------------+ |Table1 | | +--------+ | | | Table2 | | | +--------+ | | | +----------------+ Table2 is XML data source logically bound to data from Table1. Typically proposed solution was to convert the use case to single data source and use grouping. But many people cannot use this way and neither do I. My Table1 is backed by SQL and Table2 is XML data source read from url defined in Table1. With two SQL data sources the situation is easy, because I could pass the url as parameter in dataset binding property. But there is no similar way for XML datasource. I tried javascript variables, persistent variables in report context but have no luck. See attached report that simulates my scenerio. Jason wrote: I see your issue. It would be good to log an enhancement request for this option.
The key problem of cannot use property binding to solve this is that, for each query, the property binding is only evaluated once in preparation time. And for all the nested tables, they share exactly one query, that is, the property binding values cannot be changed between nested tables. We may enhance to make property binding be evaluated at query execution time rather than at query preparation time.
Gary, please evaluate if this enh can be schedule to 2.5.0. thanks
