nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Data Deploy with replicants - primary key not found

williamIV

I have a small lookup table, tbl_Practice, that I want to manage through teamsite and opendeploy. My DCR looks like this:

100
practice1

200
practice2

The data-deploy config file looks like this:

area="$workarea^"
area-type="os-filesystem"
xml-type="custom">

and my error:

DBD: TUPLE={root/0/Practice/1/PracticeName/0=practice2, IWOV_PROC_FLAG=true, state=Original, root/0/Practice/1/PracticeId/0=200, root/0=

, root/0/Practice/0/PracticeId/0=100, root/0/Practice/1=

, root/0/Practice/0=

, root/0/Practice/0/PracticeName/0=practice1, path=templatedata/Configuration/Practice/data/this}
DBD: ERROR:Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].
DBD: ERROR:Exception occured: Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].
DBD: ERROR:
com.interwoven.dd100.dd.InvalidSourceTupleException: Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].

I've tried all sorts of changes to the data deploy file, read through all the posts here and, of course, the documentation to no avail. Any ideas what is happening here?

Find more posts tagged with

Comments

williamIV

Boy that post got mangled... I put the dcr, and data deploy config along with the error message in the attached txt.

Adam Stoller

For those who cannot figure out how to read your mis-formatted post...

I have a small lookup table, tbl_Practice, that I want to manage through teamsite and opendeploy. My DCR looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<root>
    <Practice>
        <PracticeId>100</PracticeId>
        <PracticeName>practice1</PracticeName>
    </Practice>
    <Practice>
        <PracticeId>200</PracticeId>
        <PracticeName>practice2</PracticeName>
    </Practice>
</root>
The data-deploy config file looks like this:
<data-deploy-configuration>
  <data-deploy-elements filepath="C:/Interwoven/OpenDeployNG/etc/database.xml"/>
  <client>
    <deployment name="deployment">
      <source>
        <xml-source 
                 area="$workarea^" 
                 area-type="os-filesystem" 
                 xml-type="custom">
          <path name="$dcr^"/>
        </xml-source>
      </source>
      <destinations>
        <database use="$database^" update-type="standalone">
          <dbschema>
            <group name="Practice" table="tbl_Practice" root-group="yes">
               <attrmap>
                <column name="PracticeId" data-type="INT" value-from-field="Practice/[0-10]/PracticeId"/>
                <column name="PracticeName" data-type="VARCHAR(50)" value-from-field="Practice/[0-10]/PracticeName"/>
              </attrmap>
              <keys>
                <primary-key>
                  <key-column name="PracticeId"/>
                </primary-key>
              </keys>
            </group>
          </dbschema>
        </database>
      </destinations>
    </deployment>
  </client>
</data-deploy-configuration>
and my error:

DBD: TUPLE={root/0/Practice/1/PracticeName/0=practice2, IWOV_PROC_FLAG=true, state=Original, root/0/Practice/1/PracticeId/0=200, root/0=
, root/0/Practice/0/PracticeId/0=100, root/0/Practice/1=
, root/0/Practice/0=
, root/0/Practice/0/PracticeName/0=practice1, path=templatedata/Configuration/Practice/data/this}
DBD: ERROR:Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].
DBD: ERROR:Exception occured: Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].
DBD: ERROR:
com.interwoven.dd100.dd.InvalidSourceTupleException: Values for PK column [PracticeId] missing in [templatedata/Configuration/Practice/data/this].

I've tried all sorts of changes to the data deploy file, read through all the posts here and, of course, the documentation to no avail. Any ideas what is happening here?

Dwayne

I believe that the problem is that you're using replicant path syntax (the [0-10] construct) without telling DD that this IS in fact a replicant.

I'm not sure that you're going to be able to manage this table in this way using DataDeploy. I don't think that the root group can be a replicant. If you add another table to act as the root, which contained just a column that mapped to the PATH attribute, you could make your "real" table be a child of that table. Though, you'd have to add a column to be the foreign key mapping back to the new table.

williamIV

Maybe I am not understanding what a replicant is in this context. I just want to have dcr that maps to a table in the database so it can be changed within interwoven and also used as the source for dropdowns in other DCTs. Is there a simpler way to do this?

Adam Stoller

Maybe I am not understanding what a replicant is in this context. I just want to have dcr that maps to a table in the database so it can be changed within interwoven and also used as the source for dropdowns in other DCTs. Is there a simpler way to do this?

Consider using Perl (or Java?) DBI code for interacting with the DB and deploying / storing information from / into a DCR format. However, it sounds like you need to understand a bit more about DCT and DCR format/structure so you should probably spend some time with the FormsPublisher Developer's Guide and other such manuals first.

Dwayne

Maybe I am not understanding what a replicant is in this context. I just want to have dcr that maps to a table in the database so it can be changed within interwoven and also used as the source for dropdowns in other DCTs. Is there a simpler way to do this?

I think I understand your requirement pretty well. I just don't think that DD is well suited to managing that particular table, at least not using your existing DCT.

You have a replicant by virtue of the fact that you've got multiple <Practice> elements that you're managing from a single DCR. DataDeploy, to the best of my knowledge, requires that there be exactly one row in the root group which corresponds to a DCR. You're trying to define multiple. With the schema that you've layed out, there is no way for DataDeploy to be able to look at a given row in your database, and know which DCR it came from. You may know that there's only ever one DCR, but DataDeploy has no way of knowing that.

If you want to manage this table with DataDeploy, then I think you're going to need to change your architecture, and have one DCR for each row, rather than one DCR that maps to all rows.