- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @Jyoti_Yadav ,
Yes indeed, I use the French language on the Adobe Campaign software
. My apologies for your comprehension.
You have fully understood the error reported.
The error indicates that the nms:operation and internalname key element = MD_OPER19_SAP_JANVMAAT is missing in the package I am trying to import into another instance.
To answer your questions:
a) If I only import nms:centralCatalog I would have the same error because in Adobe Campaign we have an association between nms:centralCatalog and nms:operation below a screenshot:
2) In the import instance the same internalName campaign does not exist.
3) The campaign file exists in the import instance.
For me the problem is when exporting the package, the output file does not contain the nms:operation data I need to install it in another instance.
As shown above, the contents of the package export just show the data of nms:centralcatalog while I have two components in my package (nms:centralcatalog and nms:operation).
The definition of the package does not return any entity while the line is present in the database.
<definition automaticDefinition="false" id="nms:operation,MD_OPER19_SAP_JANV"
lineCountMax="5000" schema="nms:operation">
<where displayFilter="nom interne égal à 'MD_OPER19_SAP_JANVMAAT'">
<condition expr="@internalName = 'MD_OPER19_SAP_JANVMAAT'" internalId="1"/>
</where>
</definition>
Sorry, I’m trying to be as specific as I can, I’m available for any questions
.
Thanks,
Max ATTOU
Views
Replies
Total Likes