We know that we can export our deliveryTransactionalTemplate from stage and import to prod but that process seems to fail when exporting from Prod as the export fails because of certain branding.
The 'Brands (branding)' entity type uses a default ID ('BRDXXXXX') that may cause a conflict when importing the package. Change this name and repeat the operation.
Is there a way around this or a way to just extract the HTML to bring down to a staging environment?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @daver37819942,
Usually stage environments are configured with default branding to use on deliverytransactionaltemplates. Just make sure you have right branding selected, and under access authorization of transactional template have organizational unit set to "all" before exporting from stage environment. Also i hope you have updated the id of transactionaltemplate to customized one.
Let me know if you still get error.
Thanks, SK.
Hi @daver37819942,
Usually stage environments are configured with default branding to use on deliverytransactionaltemplates. Just make sure you have right branding selected, and under access authorization of transactional template have organizational unit set to "all" before exporting from stage environment. Also i hope you have updated the id of transactionaltemplate to customized one.
Let me know if you still get error.
Thanks, SK.
Hi @daver37819942,
Was the given solution helpful to resolve your query or do you still need more help here? Do let us know.
Thanks!
Views
Replies
Total Likes