colspan ignored when replicant added?

Please see the attachment.

When I create a DCR with one instance of a replicant it looks fine. But when I add a second instance of the replicant, all of the fields that should be affected by colspan get pushed outside of the replicant column. When I save the DCR and reopen it, the fields line up correctly. Is this a bug? Does anyone have a workaround?

Is there any way to get that replicant header (session-x in my document) to expand to the width of the entire replicant?

Find more posts tagged with

Comments

Migrateduser

From Interwoven support:

"I believe this to be associated with a known issue where items with the rowcontinue='t' attribute within replicants are not appropriately aligned when manipulating replicants. Investigating this further, there is a workaround. I believe that adjusting or adding a container to wrap the items "SessionID" through "DisplayEndDate" will help alleviate the alignment issue."

By the time we got this back the client had decided to implement the data capture with an ASP rather than with templating, and anyway changing the DCT would mean changing the DCR XML, which means changing the TPL and any other code that parses the DCRs...

Migrateduser

Apparently this is not even considered a bug. Unfortunately the workaround means changing the DCR structure, which means TPL updates, plus anywhere else that the DCR is parsed...

I believe this to be
associated with a known issue where items with the rowcontinue='t' attribute
within replicants are not appropriately aligned when manipulating
replicants. Investigating this further, there is a workaround. I believe
that adjusting or adding a container to wrap the items "SessionID" through
"DisplayEndDate" will help alleviate the alignment issue. I have tested
this solution briefly by adding 10 replicants, removing selected replicants,
and moving replicants, all with positive results.

This has been noted as a documentation issue, I apologize if this was not
made clear in my earlier e-mail.

It is planned to be resolved in a number of ways: a TechNote will be added
to our Knowledgebase, the release notes for the upcoming TS/TST Service Pack
will be annotated with a description of this solution, and these solutions
will be incorporated in the next release of our documentation as well.

Since this case cannot be progressed any further, it has been assigned to
our support coordinators for monitoring and follow-up. Our coordinators
will notify the interested customers when the documentation has been updated
to capture this resolution.