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

Moving from one workarea to another

System

I want to rename the folder outside the datacapture.cfg folder.

Example
changed folder one to folder two
//app16/default/main/site1/WORKAREA/Sales/templatedata/one/Service
into
//app16/default/main/site1/WORKAREA/Sales/templatedata/two/Service

When I do this I cannot open the existing DCR's in them because they are looking for the datacapture.cfg file in the path with folder one which is now folder two. Is there a way to point the DCR's to the new folder name?

My reasons for doing this are more complex than the example above.

Find more posts tagged with

Comments

jbonifaci

If you change the category or data-type, you need to update the 'TeamSite/Templating/DCR/Type' EA for all existing DCRs. Not to mention you also need to update templating.cfg.

~Jeff

Migrateduser

Not sure what exactly to do

Changing one to two in the templating.cfg gives me.

The category/type one/Service does not exist in templating.cfg. Please contact your system administrator

Doing nothing gives me.

Unable to find //app16/default/main/site1/WORKAREA/Sales/templatedata/one/Service
/datacapture.cfg. Please contact your system administrator.

Where and how do I make the changes?

Migrateduser

Also, what's an EAs? What's it short for?

Desktop.zip

Migrateduser

That's not what Jeff is saying.

Each generated file has three extended attributes set on it to tell it which type of template, which DCR, and which PT were used to create it. If you go moving the DCRs around (or for that matter, if you rename the data-type or the presentation template) you'll need to use the iwextattr command to update the values of those extended attributes.

You probably will want to script this. I bet if you search the forums for 'iwextattr' you might even find that some nice person has previously uploaded a script for munging EAs.

Migrateduser

I noticed some posts on iwextattr and this is what I was afraid of. Dang, that's what I was afraid of. Looks like more work that it's worth. But, it looks like an interesting challenge.

jbonifaci

It shouldn't take very long to write a script to iterate through all of the files in a workarea and set their 'TeamSite/Templating/DCR/Type' EA.

You can even write a generic reusable script that sets the EA based on the directory structure. For example, if a file is sitting at /templatedata/Category/DataType/data/directory/file, it is fairly safe to assume the DCR Type is Category/DataType from the file path. You would then set your EA accordingly:

iwextattr -s "TeamSite/Templating/DCR/Type"="Category/DataType" "Y:/store/main/branch/WORKAREA/Workarea/templatedata/Category/DataType/data/directory/file"

And then move on to the next file until you have iterated through all of the files. You would also likely only want to set this EA on files in the workarea whose path begins with 'templatedata' and whose 4th directory is 'data'.

Personally, I could write a script like this in no more than 10 minutes, so it shouldn't be all that hard for you to do either.

~Jeff

nipper

It shouldn't take very long to write a script to iterate through all of the files in a workarea and set their 'TeamSite/Templating/DCR/Type' EA.

And then move on to the next file until you have iterated through all of the files. You would also likely only want to set this EA on files in the workarea whose path begins with 'templatedata' and whose 4th directory is 'data'.

Personally, I could write a script like this in no more than 10 minutes, so it shouldn't be all that hard for you to do either.

I wrote that a couple years ago and posted it in the Tech lib. It was caled something like Templating EA utility, from June 2004. You should be able to search for it. It was written for Unix, but should work on DOS without trouble.

Andy

Migrateduser

I just finished writing a script to make a batch file (could have it run the command directly from the script, but wanted to be able to check the outcome first)


use strict; 
use warnings; 
use File::Find; 
my $localdir = '//servername/default/main/aaa/WORKAREA/bbb/templatedata/tools/ccc/data'; 
my $file = "/temp/dirindex.bat";
open FILE, ">$file" or die "unable to open $file $!";
  find(sub {print FILE 'iwextattr -s TeamSite/Templating/DCR/Type=tools/ccc ' . $File::Find::name, "\n" },$localdir);

Migrateduser

updated to list the contents of the folder that you are in


use strict; 
use warnings; 
use File::Find; 
    use Cwd;
    print cwd;
my $localdir = cwd; 
my $file = "e:/temp/dirindex.bat";
open FILE, ">$file" or die "unable to open $file $!";
  find(sub {print FILE 'iwextattr -s TeamSite/Templating/DCR/Type=tools/Model2 ' . $File::Find::name, "\n" },$localdir);