Error when duplicating a campaign.

[memmaker650]

Hello all,

We have created a new Adobe Campaign environment. And today we have noticed that when duplicating an existing operation (Campaign module) doesn't means duplicate the deliveries and workflow defined in the original operation. Now duplicate an operation works the same as create a new operation or very similar.

That's seems weird to us because in other ADC env with an upper ADC version we can do this. We think that there are any parameter/s that we has different value in one env that the new one.

We have reproduce this error with admin user and with other user with less privileges.

Anyone knows which parameter modify the way campaign module work.

Thanks in advance.

[shrawans3153003]

Hello,

Could you please let me know which version(server version) of AC you are trying this?

[memmaker650]

The error was detecting in v8754, but it works in our other env which uses v8770 in server. For both cases we use v8770 as appli version.

Also, we have continued analyzing the problem and we have noticed that the duplicated operation has no deliveries, in contrast with the original operation, but the new deliveries are created. The problem is that these deliveries have not defined the id of the operation (foreign key when looking in details is empty). If we modify it with the operation id, magically is appear in the duplicated operation.

Why we the deliveries are created unconnected with the operation?

[Adhiyan]

Hello ,

Could you please compare the packages you have deployed in both the application servers. I guess you are missing one package related to Campaign and hence the foreign key link of operation-id is missing in the delivery Schema and the mapping from delivery to Campaign does not happen.

this link may be missing in your server which connects the nms:operation and nms:delivery schema

Regards,

Adhiyan

[memmaker650 · Accepted solution]

Hello Adhiyan,

Thanks for your help. We have solved the problem. The problem was because we have migration the operation model and seems to have also any right problem. Creating a new model in the new environment solved the problem,

Thanks another time.

Regards

Jorge