Looking for guidance in promoting contenttype/pagetype's configuration to higher environment using content porter.

Web publication has 20 different content type defined/created. Used content porter to promote content to SIT all content promoted to except content types n page type configuration.

Also, child publication is not persisting content type definition.

Can some help me out what special configurations/dependencies setting required at content porter or any other configuration at wcm which solved above problem?

Additional description based on given pointers to resolved issue.

Project Specific Export based on DXA1.2

Below tag is found in the export package index.xml

> <ApplicationIds>
>         <ApplicationId>SiteEdit</ApplicationId>
>       </ApplicationIds>

Project Export However, we found 0-0-0.xml is missing in export package.

DXA 1.2 Below tag is found in the export package index.xml


Dxa 1.2 Export

<PackageItem xmlns:tcm="http://www.tridion.com/ContentManager/5.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.sdltridion.com/ContentManager/ImportExport/Package/2013">

Thanks ! Hiren

  • 1
    I'm rusty here, but Content Porter includes the ability to port "Application Data" (which is where Content Types are stored) between environments, this should be possible.
    – Nuno Linhares
    Sep 12, 2016 at 11:00
  • What does SIT mean? Sep 12, 2016 at 11:19
  • System Integration Testing - America uses a different variant of DTAP :)
    – Nuno Linhares
    Sep 12, 2016 at 13:21
  • 1
    Hi Nuno, I have verified the export package do have content type details available in "Application Data" however while importing I just try to check item mappings and getting a warning "This intermediate package contains application data with the following identifier(s): sdl.com/tridion.SemanticMapping/typeof, which does not match any application data category defined on the target Content Manager. Because of this, Content Porter will not import this application data." Sep 12, 2016 at 15:42
  • The App Data warnings are about DXA App Data used for DXA semantic mapping. Apparently, your Schema have such App Data. In that case, you should ensure you have the DXA App Data Definition XML file on your target machine. Doesn't explain why your XPM Content Types are not ported, though. Sep 12, 2016 at 16:43

1 Answer 1


I faced the similar issue when porting from current environment (DXA working) to new environment. Copying the DXA Application Data Definition.xml to [tridion home]\config\ImportExport\ApplicationData solved the issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.