Hi,
Thanks for the details.
This issue seems to be a limitation. In each of the custom controls in the event beforePageLoad, code is written to put all the information passed on to CC into sessionScope which is then utilized to generate the chart.
When the CC is put into data table and you use the collection name, it gets evaluated after the beforePageLoad event, I guess, and it is evaluated for every row.
I am currently working on next version and I will look into this. But I cannot guarantee if I would be able to come up with a fix for this one as the current architecture may not be able to handle this. So I am forced to think if CC is put into repeat control it may give the same issue, I haven't tried it though.
Thanks for pointing out this issue.
Regards,
Naveen