Enterprise Client Community

Hi,

I think I've a special constellation (once again ;-))

I have a grids rendered within a repeat component, then I try to set the render property by .{render} the property is defined within the class which is the type of the list set in the repeat component. But it seems to get mixed up with the reference of the grid items properties which also have the form .{xxx} so the result is that the column isn't rendered even when render == true

regards
Markus

Hi Markus,

we can reproduce in an own example... Just working on it...

Thanks a lot!!! - Björn

Hi Markus,

the interim build 20220312_INT1 contains the fix.
It is available in the CaptainCasa-Maven-Repoisitory (www.CaptainCasa.com).

Thanks again! Björn

thx, for that quick fix

I had another problem with fixgrid within a repeat, maybe it's solved too, I haven't tried the interim version.

When using a t:gridfooter where e.g. a total is calculated. The total is calcualted on item scope as the general property i mentioned before in the gridfooter I reference by .{totalAmount}

BR
Markus

Yes, same problem. Should now be fixed... - Björn

Hi,

now I found another problem

I want to create the fixgrid dynamically (with t:dynamiccontent)

there is a problem with the expression

when I do
LABELNode label = new LABELNode();
label.setText(".{type.descriptionT}");

it generates
#{d.EventsPB.events[0].type.descriptionT}

but it should be
#{d.EventsPB.events[0].gridEvent.rows[0].type.descriptionT}

BTW events is the Collection for t:repeat it contains the fixgrid gridEvent

regards
Markus

Hi Markus,

we need a bit more details about the structure: where is REPEAT, where is ROWDYAMICCONTENT? A mini demo program/XML page would be highly appreciated. ;-)

Kind regards! Björn

sorry, I add JSP and class

In the row should be name = "Test Row" but it takes the name from the repeatItem

...thanks! Can reproduce it... - Björn

FYI

could solve the problem using a pagebean which includes the dynamic content in the repeat component

Hi,
very tricky way to bypass the inner problem! We are currently testing our bug fix for potencial collateral damage... The fix is contained in next Monday's version. If you want to have an interim update - just tell us!
Kind regards! Björn

no hurry, monday is ok

thx