Skip to main content
Commonmark migration
Source Link

Using the Content Porter API we're building on the idea of the [DTAP-it extension from Jaime and Warner][1]DTAP-it extension from Jaime and Warner

One issue we have is the XmlName of the Category is different from Dev and ACC, and this is causing problems.

I recall in the past we would sometimes manually hack the Content Porter XML export definitions and change the Publication name, for example, to re-arrange the blueprint.

Would it be reasonable to do the same thing here, hacking the CP export XML and changing the Category XML name to be the same as the destination server?

Is there a cleaner way? [1]: http://jaimesantosalcon.blogspot.de/2015/06/dtap-it.html

Using the Content Porter API we're building on the idea of the [DTAP-it extension from Jaime and Warner][1]

One issue we have is the XmlName of the Category is different from Dev and ACC, and this is causing problems.

I recall in the past we would sometimes manually hack the Content Porter XML export definitions and change the Publication name, for example, to re-arrange the blueprint.

Would it be reasonable to do the same thing here, hacking the CP export XML and changing the Category XML name to be the same as the destination server?

Is there a cleaner way? [1]: http://jaimesantosalcon.blogspot.de/2015/06/dtap-it.html

Using the Content Porter API we're building on the idea of the DTAP-it extension from Jaime and Warner

One issue we have is the XmlName of the Category is different from Dev and ACC, and this is causing problems.

I recall in the past we would sometimes manually hack the Content Porter XML export definitions and change the Publication name, for example, to re-arrange the blueprint.

Would it be reasonable to do the same thing here, hacking the CP export XML and changing the Category XML name to be the same as the destination server?

Is there a cleaner way?

Tweeted twitter.com/#!/StackTridion/status/648713518674542592
Source Link
robrtc
  • 10.2k
  • 2
  • 16
  • 35

Tridion Category XmlName with Content Porter

Using the Content Porter API we're building on the idea of the [DTAP-it extension from Jaime and Warner][1]

One issue we have is the XmlName of the Category is different from Dev and ACC, and this is causing problems.

I recall in the past we would sometimes manually hack the Content Porter XML export definitions and change the Publication name, for example, to re-arrange the blueprint.

Would it be reasonable to do the same thing here, hacking the CP export XML and changing the Category XML name to be the same as the destination server?

Is there a cleaner way? [1]: http://jaimesantosalcon.blogspot.de/2015/06/dtap-it.html