Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DataDeploy Multiple Replicants
liladhar
We have created a addresses_dd.cfg file.
The nested level is like this:
Table 1 (addresses):
PK Field1a
PK Field1b
Field1c
Table 2 (addressname):
PK field2a
PK FK field1a
PK FK field1b
field2b
The Table 1 is a replicant. We are using two primary keys from Table 1 as foreign-primary keys for Table2 (addressnames). It creates the tables successfully however while deploying the data, throws the following error:
ERROR:Incorrect mapping in group [addressname]
ERROR:Multiple replicants of the same level are allowed only at the innermost nested level.
We are using the Teamsite DataDeploy Version 5.2.
This is really an urgent issue and earlier reponse will be appreciated.
Find more posts tagged with
Comments
Migrateduser
Like the message says you probably have columns from non-innermost level (or non-leaf level ) nodes mapped in the group which is not supported. This is supported in DD5.6 SP1 which requires TeamSite 5.5.2.
The best approach would be to map the problematic nodes to different groups and use table joins for retrieval.
liladhar
We upgraded to a newer version but still the problem persists!
Can you please tell me any example for such case which works with DataDeploy 5.6 with service pack 1?
Thanks
Migrateduser
Did you upgrade TeamSite too? DD 5.2.x is compatible with TS 5.0.x, whereas DD 5.6 is compatible with TS 5.5.2 and higher. Just want to make sure you aren't mixing versions.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
liladhar
Yes we did and currently running with TS 5.5.2 with Service Pack 2. Is that adequate? Awaiting for your reply
Migrateduser
Should be. You may want to open a case with Tech Support to help you resolve this.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
catorarn
Interwoven support is researching this at the moment. This is the outcome: The following configuration deployed:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<data-deploy-configuration>
<client>
<deployment name="basearea">
<source>
<xml-source options="wide" area="/default/main/datadeploy/WORKAREA/work" area-type="ts-filesystem" xml-type="interwoven">
<path name="templatedata/internet/book/data" visit-directory="deep"/>
</xml-source>
</source>
<destinations>
<database db="10.101.1.98:1433?database=multipleselectbox" user="sa" password=".20whc!" vendor="microsoft-inetuna" update-type="standalone" state-field="state" delete-tracker="yes" enforce-ri="no">
<dbschema>
<group name="Reviews" table="Reviews" root-group="yes">
<attrmap>
<column name="Review_Reader" data-type="VARCHAR(255)" value-from-field="Reviews/[0-4]/Review Reader" is-replicant="yes" allows-null="no" is-url="no"/>
<column name="Select_expertise" data-type="VARCHAR(255)" list-to-replicant="yes" list-field="Reviews" value-from-field="Reviews/[0-4]/Select_expertise" is-replicant="yes" allows-null="yes" is-url="no"/>
<column name="Review_Reader_E_Mail" data-type="VARCHAR(255)" value-from-field="Reviews/[0-4]/Review Reader E-Mail" is-replicant="yes" allows-null="yes" is-url="no"/>
<column name="Reader_Comments" data-type="VARCHAR(255)" value-from-field="Reviews/[0-4]/Reader Comments" is-replicant="yes" allows-null="yes" is-url="no"/>
</attrmap>
<keys>
<primary-key>
<key-column name="Review_Reader"/>
</primary-key>
</keys>
</group>
<group name="Select_expertise" table="Select_expertise" root-group="no">
<attrmap>
<column name="Review_Reader" data-type="VARCHAR(255)" value-from-field="Reviews/[0-4]/Review Reader" is-replicant="yes" allows-null="no" is-url="no"/>
<column name="Select_expertise" data-type="VARCHAR(255)" list-to-replicant="yes" list-field="Reviews/[0-4]/Select_expertise" value-from-field="Reviews/[0-4]/Selectlist/[0-5]/selectval" is-replicant="yes" allows-null="no" is-url="no"/>
</attrmap>
<keys>
<primary-key>
<key-column name="Review_Reader"/>
<key-column name="Select_expertise"/>
</primary-key>
<foreign-key parent-group="Reviews">
<column-pair parent-column="Review_Reader" child-column="Review_Reader"/>
</foreign-key>
</keys>
</group>
</dbschema>
</database>
</destinations>
</deployment>
</client>
</data-deploy-configuration>
I changed the replicant fields (except for the multiple select list Select_expertise) back to [0-1] and that also deployed. Deployments were made to a SQL2k db. The Select_expertise table consisted of 8 rows as I filled in 2 Reviews replicants and then selected all options from Select_expertise.
Edited by catorarn on 07/08/04 04:16 AM (server time).