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

Migrating old DCRs to new DCT fromats using PERL script

msr

Hi,

We have a requirement to migrate the existing DCR generated content to new DCT form. Following is the sample for our migration.

Existing page Info:
HTML path: pages/test1.html
DCR Path: templatedata/pages/landing_page/data/test1.xml
DCR Fields: Title,Body

After migration File information need to be as follows

HTML path: pages/test1.html
DCR Path: templatedata/pages/general_page/data/test1.xml
DCR Fields: Title,Body,Image,Keywords (Added New fields)

Could you pls suggest an approach to complete this task

Environment
Teamsite 6.5
Unix

Thanks
MSR

Find more posts tagged with

Comments

Adam Stoller

Could you pls suggest an approach to complete this task

Based on the information provided - I'd say hire someone who knows what they're doing.

Obviously (hopefully) you'll have to change the EAs on both the DCR and the generated file to match the new data-type (though the generated file should just get re-generated to take care of that, once the DCR's EAs are fixed.

Is the structure of the DCT actually changing or are you just adding more fields to the existing structure? If the latter, moving the DCR and re-setting its EA should be sufficient. If the former, then you have a lot more work cut out for you.

modify_opacity.rptdesign

nipper

And, oh, by the way, think about upgrading as your install is 5-6 years old.

Changing the DCR type from landing_page to general_page is also quite stupid. It buys you noting but a headache. Don't do it (unless you are splitting it into multiple DCR types)

Add the new fields and make the users edit and change the data, or write a script to add the data, but adding blank fields is of no value, so if you do that have the correct data.