Is the following a known bug or a new security setup under Adobe Campaign Classic? | Community
Skip to main content
A
assiba_johnson
Level 2
January 31, 2024
Question

Is the following a known bug or a new security setup under Adobe Campaign Classic?

  • January 31, 2024
  • 1 reply
  • 834 views

We have upgraded our beta instance to 9368:

 

 

Today we tried to import a package of transactional emails template into the beta instance and got the following error:

 

We found the root cause which is the duplicate key as shown above.

The solution or workaround is to remove the FCPSeed data from the XML package before the import:

 

 

Is anyone can confirm if this is a bug or an expected behavior under the new build? 

 

Thanks in advance!

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Manoj_Kumar
Community Advisor
Manoj_KumarCommunity Advisor
Community Advisor
February 1, 2024

Hello @assiba_johnson 

 

This is not a bug.

 

internalName is unique for each record and you can have only one record for an internalName.

 

With this package, the Adobe campaign was trying to create a new record with the existing internalName and that is why you see this error.

Manoj  | https://themartech.pro
A
assibaj68720939
February 1, 2024

Hi @_manoj_kumar_ ,

 

Please see my comment about the build version.

This is working fine under build 9356.

The error is related to the nmsseedmember_id. Of course related to the internalName.

Here is what we did:

 

- We exported a transactional email template as XML package from an ACC instance with build 9356 and tried to import it to an instance with build 9368 --> KO

 

-  We exported a transactional email template as XML package from an ACC instance with build 9356 and tried to import it to an instance with build 9356 --> OK

 

It seems that under the new build 9368, there is an extra check on the FCPSeed section in the XML while importating the transactional email template . So if already exists under the targeted instance, the package import fails. 

 

I also highlighted the workaround to fix it. Please review my first comment. Is this a bug or an expected behaviour under the new buiild?

 

Thanks in advance!

 

Terms & ConditionsAccessibility statement

Loading footer...