This content has been marked as final. Show 4 replies
That's the intended behavior. It would be impossible to anticipate any HTML structure customers would want to use in their templates, on the other hand though, we do want to keep it open and not lock those templates down. So in your case, I suggest going with a nested table within the TR row, this way you can maintain your single-TR per tabular form ROW, yet within those rows, have your own table structure,
thanks for the quick reply.
I was afraid you would say it is intended behavior :-)
A table per row has the disadvantage of loosing the automatic column width, i would have to set the column width to a fixed value to maintain a nice look.
Well, thanks for the moment, i'll try to find a general solution and (if i succeed) get back to you.
i just tried to workaround my problem and wrapped my 2 rows in a TBODY Tag, but APEX still attaches the "init_row_xxxxx" id to the first TR it finds.
I think it could/should use the first tag it encounters as a starting point for the sample row.
What do you think?
It's using the first TR, I'm sure there are cases where that's not ideal. It's designed to work with the standard report templates provided by APEX. Any custom built templates will have follow that structure. There really isn't much we can do about this at this stage, at least not for 4.0 / 4.0.1. We can take a look at making this customizable in 4.1, i.e. keep the current behavior as the default, but allow to configure this to allow for alternate structures.