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; } } }

Same templatedata path in Different Branch

cliffhanger

Hi All,
We have multiple branches with identical "templatedata" structure. They are different in their content only.

The problem we're having is, DCR_A in branch X is getting overwritten by the data from DCR_A in branch Y or vice versa depending on which one was deployed last. Dadadeploy is considering them as the same DCR and overwriting ones record with another since they share the same relative ptah: templatedata/CATEGORY/DATATYPE/DTA/DCR_A.dcr

I am executing standalone deployment.

Can DD be configured so that is uses ABSOLUTE path rather than RELATIVE path entry in its cache??

Any input is appreciated!!

Thanks
-cliff
TeamSite 6.1, DD 5.6

Edited by cliffhanger on 10/07/05 01:45 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Cliff,

Can you post you config file and log? Are you not seeing the branch name in the DD tracker table?

Mariam

cliffhanger

We're doing a standalone deploy, so do not maintain deltracker table. But I am sure DD is keeping track of the DCRs internally through some table where it maintains only the templatedata path.

We opened a support ticket on this, but the support person suggested there's no other way than naming the DCRs uniquely. This does not quite make sense to me, if the filepaths are indeed different because of different branch, there should be some way of telling DD to treat them as different although they share the same templatedata path. Keeping track of dcr name uniqueness across branches, workareas, would be a nightmare!! Plus, if the filesystem is able to differentiate them, shouldn't DD be able to do the same?

Here's the relevant snippet of the DD config:
<client>
<deployment name = "dd_productDetail">

<source>

<teamsite-templating-records
options = "differential,wide"
custom = "yes"
area = "/default/main/Mktg_US/STAGING"
base-area = "/default/main/Mktg_US/EDITION/SOME_EDITION">
<path name = "templatedata/CATEGORY/DATA_TYPE/data" visit-directory = "deep" />
</teamsite-templating-records>
</source>
<destinations>
<database use = "IWUI"
update-type = "standalone"
delete-tracker = "yes"
log-level = "3"
real-update = "yes">

Appreciate any insight to this problem, or an explanation.....

Thank you,
-cliff

Migrateduser

Can you post config files that we can use to reproduce this?

Mariam

cliffhanger

Mariam,
I am attaching the config file.

Thanks
-cliff

cliffhanger

Okay, we have a solution.

We were using "path" field in the root group. So, datadeploy assumedtemplatedata path(assumption assumption assumption!!

) as its base to keep track of DCR records, and did not use 'iwdeltracker' table. That's why dcr with same templatedata path in one branch was overwriting the other one's record.

Workaround to this issue:
We are setting metadata with the 'path' value using PreProcessor, and using that value instead of "path", and DD is using iwdeltracker table which keeps track of both the templatedata path and the area, and solves our problem!!

Migrateduser

Thanks for the update. I've asked Support to file a feature request for DD to use the real PK, not the path when doing selects or to use the absolute path, not relative path for the select... that was a tricky one.

Mariam