Container replicants duplicated on read

There's a very strange problem in my DCT where containers A, B, and C are duplicating replicants. Each container has one default child replicant. I save to a DCR with one replicant per container (and the saved xml looks good). But when I try to open the DCR, each container has 2 extra replicants. 1) I did notice a pattern in how my containers in A, B, and C were being read. The good and 'bad extra' containers were created and displayed in this order. Could it also be that some of the child containers are of differing types? If so, how can we have this functionality and still read / write data correctly?

A) contentFeatureSet (contentFeatureMain, contentFeature)
contentFeatureSet (bad extra)
contentFeatureSet (bad extra)

contentFeatureSet (bad extra)
contentFeatureSet (contentFeatureMain, contentFeatureDescription, contentFeature)
contentFeatureSet (bad extra)

C) contentFeatureSet (bad extra)
contentFeatureSet (bad extra)
contentFeatureSet (contentFeatureLeftColumn, contentFeature)

I'm using ContentCenter Professional, Version: Interwoven TeamSite 6.7.1.0

Thanks for any help
Tim

Find more posts tagged with

Comments

madhug

Tim,

Can u post your dct. It will be easy to debug.

Regards,
Madhu

twashing

Sure. The DCT and an example DCR is attached which have just clips of the relevant sections, due to file size restrictions).
datacapture.cfg.txt
index_20080515-0900.txt

I've since realised that the 3 DCT contentFeatureSets are correctly writing out 3 <contentFeatureSet/> tags. But I want to treat those 3 tags as 3 different types. When opening the DCR however, ContentCenter Pro sees the 3 <contentFeatureSet/> DCR (xml) tags and loads all 3 into my first contentFeatureSet. Then the same thing happens in the second contentFeatureSet and so on.

What I want is to have the first DCT contentFeatureSet treat the first <contentFeatureSet/> in my XML as a separate type as the second <contentFeatureSet/>. I've tried the 'refid' container attribute to no avail

Hope this makes sense.

Phanie

Tim, I looked at your posted dct & xml the day you posted it but I couldnt figure out why it was behaving like that on read. wanted to know if everything is working fine now and also the cause for dcr being shown like that intially.

--
Phanie

Sure. The DCT and an example DCR is attached which have just clips of the relevant sections, due to file size restrictions).
datacapture.cfg.txt
index_20080515-0900.txt

I've since realised that the 3 DCT contentFeatureSets are correctly writing out 3 tags. But I want to treat those 3 tags as 3 different types. When opening the DCR however, ContentCenter Pro sees the 3 DCR (xml) tags and loads all 3 into my first contentFeatureSet. Then the same thing happens in the second contentFeatureSet and so on.

What I want is to have the first DCT contentFeatureSet treat the first in my XML as a separate type as the second . I've tried the 'refid' container attribute to no avail

Hope this makes sense.

twashing

Hi Phanie. At the end of the day, I had to refactor the 3 DCT contentFeatureSets into 1 contentFeatureset. I control the replicant length via javascript. It was a huge pain, but that was the solution.

In my DCT, I had 3 named containers called 'contentFeatureSet'.
<container name='contentFeatureSet' location='contentFeatureSet'>
<container name='contentFeatureSet' location='contentFeatureSet'>
<container name='contentFeatureSet' location='contentFeatureSet'>

Initially creating and writing out an DCR using this, rightly creates an XML with 3.
<contentFeatureSet>
<contentFeatureSet>
<contentFeatureSet>

The read was breaking because each <container name='contentFeatureSet' /> read all the <contentFeatureSet>. The name of the XML tag is what tells the DCT container to read in. So all 3 DCT containers read all 3 <contentFeatureSet>. This created 9 Content Feature Sets in my UI, instead of the desired 3. So like I said, I refactored the 3 DCT contentFeatureSets into 1 contentFeatureset, and manipulate their range via javascript.

Tim

Phanie

thanks Tim on updating me on your issue.
I was thinking issue was with refid and missing or anyways its now resolved thanks again.

--
Phanie