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

error in deploying from current edition

Richu

Hi All,
PFA the config file for deploying the metadata.There is no problem is the script. It is succesful, but no metadata is deployed in the database but when I give the the area as /main/KMS/EDITION/ed_0002 instead of the /main/KMS/EDITION , it works fine and metadata is deployed successful.

But as per the manuals "deployment configuration guide" : By using the TeamSite paths for EDITION and IW_PREV , you can automatically specify the current or next to the most current edition without having to modify the deployment configuration.

As per my requirement, if the EDITION folder has say 5 folders then my source should be EDITION/folder2. Also I dont want to hard code the edition name. it should automatically take the latest edition.

Has anyone come across this error?Please Help!!! It is very urgent.

Thanks,
Richa

Find more posts tagged with

Comments

Adam Stoller

Hi All,
PFA the config file for deploying the metadata.There is no problem is the script. It is succesful, but no metadata is deployed in the database but when I give the the area as /main/KMS/EDITION/ed_0002 instead of the /main/KMS/EDITION , it works fine and metadata is deployed successful.

But as per the manuals "deployment configuration guide" : By using the TeamSite paths for EDITION and IW_PREV , you can automatically specify the current or next to the most current edition without having to modify the deployment configuration.

As per my requirement, if the EDITION folder has say 5 folders then my source should be EDITION/folder2. Also I dont want to hard code the edition name. it should automatically take the latest edition.

Has anyone come across this error?Please Help!!! It is very urgent.

Thanks,
Richa

I haven't checked the manuals, but I believe the "magic" token "EDITION" (and "IW_PREV") only applies to OpenDeploy (not DataDeploy) - so what you need to do is something like:

...
<teamsite-extended-attributes                   
                        options = "wide"
    area="main/KMS/EDITION/$edname"> 
...

and pass in the edition name on the command line (-k edname=...) which you can easily get via CLTs like iwlasted or through various other means.

Rick Poulin

As per that very same documentation, you do need to specify the store.
Try area="/default/main/KMS/EDITION"

I suspect that if that works and the other one doesn't, that just may be a fluke.

If that still doesn't work, please post your OD version.

Richu

Thanks a lot adam .. Its done!! yippy!!! Smiley Happy

Also adding storename doesnot work as it automatically appends the store name..

Thanks,
Richa

Adam Stoller

Thanks a lot adam .. Its done!! yippy!!!
Also adding storename doesnot work as it automatically appends the store name..

Thanks,
Richa

Actually you should include the store name (I missed that, as I was concentrating on the end of the path) - the fact that it assumes /default/main/... does not mean you shouldn't be explicit about it.