Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
datadeploy substitution problem
pietje
Hi,
In our datadeploy we want to change a string to a value given by a parameter.
For this we are using the substitution tag.
<substitution name="GlobalSubstitution">
<field name="TEXT" match="localhost:8080" replace="$prp" global="yes"/>
</substitution>
The problem with this substitution is that in the clob the name is replaced by $prp and not by the value of $prp.
We now the value $prp is working for the were-clause that we use a couple of lines up.
Any solutions?
Greetings Patrick
Find more posts tagged with
Comments
pflory
Patrick,
SImilar to OpenDeploy, these tokens must look like:
$replaceMe^
not just
$replaceMeNot
You need the trailing carot.
Is that the problem here?
-Paul
Paul Flory
pietje
Hi Paul,
I tried that but that isn't solving the problem. Intsead of replacing it with $prp it is replaced with $prp^ and not with the contents of $prp.
I get the feeling it is some kind of bug. We are using teamsite 5.5.2.
Greetings Patrick
Migrateduser
what version of DataDeploy is installed, and what Service Pack level?
lissa
pietje
Hi lissa,
teamsite 5.5.2
Service pack 5.0
DataDeploy Version = 5.6.0
Patrick
Migrateduser
the field name from the DCR is probably incorrect:
<field name="TEXT"
it is most likely not named TEXT, but some other name, check your DCR field your getting this value from, it should be the same!
Interwoven Certified Technical Support Engineer
shegg@Interwoven.com
"> Email:
shegg@Interwoven.com
pietje
TEXT isn't the name of a dcr but the name of a field in the database. The name of a CLOB field to be precise.
It should chang an internet address from the test enviroment address to the production address.(it is a generated html file)
The problem is that it isn't changing the address to the conntent of the perl variable $prp but with the text "$prp".
Migrateduser
Patrick,
Is this specific to CLOB fields? Can you try a non-clob field and see what happens? this is a basic feature so I am wondering if there is some bug related to clobs.
Mariam