Implementing tabbing functionality in DCT

Hello everyone,

We are using teamsite version 6.7.1.
All the DCRS of templates are currently in "iwov" format.For one requirement we need to implment tabbing in the DCT.Tabbing is supported only for the xml format so the existing DCRS are not opening up.
We are planning to do the conversion using the script but we are stuck as all the dcts have different containers and depth of each container is different.Not sure if we are applying the right logic.
What logic we can apply so that common script can handle all the DCTs for conversion from iwov to xml.Please suggest.

Find more posts tagged with

Comments

Rick Poulin

What logic are you currently applying, and what's not working about it? Do you have so many DCT types that you need a scripted solution?

Adam Stoller

The conversion of the DCTs should be relatively easy.
The conversion of pre-existing DCRs, FormAPI code, and PTs tends to be much more involved.
I recommend making sure you have a good base-line edition in the branch(es) where you are planning to do this (also hopefully being worked on in a DEV environment before attempting to run the process in PROD) - make sure your script generates lots of diagnostic output for anything that doesn't match the coded expectations - run the script, check the log, restore the edition, fix the script and repeat the above steps until you believe you have everything working.

I did something like this a few years ago and found that utilizing mapping / configuration files for the script eased a lot of the debugging/fixing issues - but I still had to be careful about things that didn't match expectations (like where your FormAPI code uses concatenation to fiddle with an xpath for an item)

I find such challenges fun - hopefully you'll embrace it as such too - it makes it far more interesting to work on rather than looking at it as an excruciating chore ;-)