Root group with replicants

Hi everyone!

I came across issues with having replicant values in the root-group and my suspicion is that it is because DD perhaps does not like replicant value in the root-group. I searched the manuals, but could not find such reference.

Is it documented anywhere that a "there should be exactly one row in the root group" for a DCR?

Thanks
-cliff

Find more posts tagged with

Comments

Adam Stoller

Hi everyone!
I came across issues with having replicant values in the root-group and my suspicion is that it is because DD perhaps does not like replicant value in the root-group. I searched the manuals, but could not find such reference.

Is it documented anywhere that a "there should be exactly one row in the root group" for a DCR?

Thanks
-cliff

Are you talking about a replicant within the root-group or having the root-group be a replicant container itself?

The former should be possible.
The latter I do not believe is possible.

cliffhanger

Are you talking about a replicant within the root-group or having the root-group be a replicant container itself?

Could you please explain the difference? They both seem the same to me

Thank you,
Cliff

Adam Stoller

Are you talking about a replicant within the root-group or having the root-group be a replicant container itself?

Could you please explain the difference? They both seem the same to me

Thank you,
Cliff

A replicant within a root-group would be something like:

<root_group>
    <replicant_container>
        <item>value-1</item>
    </replicant_container>
    <replicant_container>
        <item>value-2</item>
    </replicant_container>
    <replicant_container>
        <item>value-3</item>
    </replicant_container>
</root_group>

A root-group as a replicant would be like:

<root_group_replicant>
    <item>value-1</item>
</root_group_replicant>
<root_group_replicant>
    <item>value-2</item>
</root_group_replicant>
< root_group_replicant>
    <item>value-3</item>
</root_group_replicant>

Which would be invalid XML because you cannot have multiple root elements.

cliffhanger

Hmm got it! Perhaps I was not clear in my explanation of the problem.

The first scenario you mentioned is the problem. In your first reply you've mentioned that it should be possible to deploy a replicant within a root-group , but I think it is not because I've tried it, and it only deploys the first record in the replicant.
Here's the snippet from my DD config:

  <group name="pageCrossRef" table="PAGE_METADATA" root-group="yes">
  <attrmap>
  <column name = "URL" data-type="VARCHAR2(500)" value-from-field="productDetail/0/url/0" allows-null="no"/>
  <column name="NAME" data-type="VARCHAR2(100)" value= "CROSS_REF" allows-null="no"/>
  <column name="VALUE" data-type="VARCHAR2(2000)" value-from-field="productDetail/0/crossRef/[0-4]/crossRefLink/0" allows-null="no" is-replicant="yes" />
  <column name = "SORT_ORDER" data-type="INTEGER" replicant-order-column ="yes" value-from-field="dummy" allows-null="no" />  
  <column name = "TEAMSITE_PATH" data-type="VARCHAR2(500)" value-from-field="path" allows-null="no"/>
  <column name="DATE_CREATED" data-type="DATE" value-from-field="TeamSite/Metadata/Creation_Date_Time" data-format="EEE MMM dd HH:mm:ss yyyy" allows-null="no" db-datetime-format="DY MON DD HH24:MIS YYYY" />
  <column name="CREATED_BY" data-type="VARCHAR2(500)" value-from-field="TeamSite/Metadata/Creation_Who" allows-null="yes"/>
  <column name="DATE_MODIFIED" data-type="DATE" value-from-field="TeamSite/Metadata/Update_Date_Time" data-format="EEE MMM dd HH:mm:ss yyyy" allows-null="yes" db-datetime-format="DY MON DD HH24:MIS YYYY"/>
  <column name="MODIFIED_BY" data-type="VARCHAR2(500)" value-from-field="TeamSite/Metadata/Update_Who" allows-null="yes"/>
 </attrmap>
  <keys>
  <primary-key>
  <key-column name="NAME"/>
  <key-column name="URL"/>  
  <column name = "SORT_ORDER"/>  
  </primary-key>
  </keys>
 </group>

Am I missing something here?

By the way, why does the editor remove XML tags from the post unless I put the magic "<x>" in there?

Thanks
-cliff

Adam Stoller

Hmm got it! Perhaps I was not clear in my explanation of the problem.

The first scenario you mentioned is the problem. In your first reply you've mentioned that it should be possible to deploy a replicant within a root-group , but I think it is not because I've tried it, and it only deploys the first record in the replicant.

<column name="VALUE"
        data-type="VARCHAR2(2000)"
        value-from-field="productDetail/0/crossRef/[0-4]/crossRefLink/0"
        allows-null="no"
        is-replicant="yes"
        />

Try removing the highlighted portion above and see if that works. I think the static '/0' confuses the replicant processing. Removing it would also be consistent with all the examples in the documentation as far as I can tell.

By the way, why does the editor remove XML tags from the post unless I put the magic "<x>" in there?

Thanks
-cliff

Because it's attempting to interpret the elements as HTML - I believe if you surround the code with [html]...[/html] you won't need to use the <<x>yyy>...<<x>/yyy> syntax - but I think you lose the 'pre'-style interpretation which maintains white-space.