Expand my Community achievements bar.

We are excited to introduce our latest innovation to enhance the Adobe Campaign user experience — the Adobe Campaign v8 Web User Interface!
SOLVED

Need to customize delivery form

Avatar

Level 3

Hi all,

During post upgrade activity, attributes added in adi:delivery  reflected in nms:delivery and made the changes in nms:delivery form due to the same. Everything was deleted after upgrade.

Please suggest the solution related to the same. Do we need to create seperate form named as adi:delivery that will be mapped with nms:delivery schema and also created the adi:delivery schema.

Kindly help.

Regards,

Nidhi

1 Accepted Solution

Avatar

Correct answer by
Level 10

Hello Nidhiv,

It seems that this ticket is a bit correlated to your previous one:

Extension of input form into another input form in Neolane

As said in the other ticket, there are extensions for schemas but not for forms, so you must modify the factory form for a schema extended as for factory schema.

Moreover, during a postupgrade operation (upgrading towards a new build), the postupgrade log file(s) (one per instance) warn(s) about the discrepancies between the current version and new version of all objects (schemas, forms).

Actually it keeps the current version and the admin people have to choose what action to do in the Admin>Settings>Conflict management node.


You can keep the current version, accept the new one, or merge manually in order to keep what you customized and adding the new elements brought by the new version/build.
Did you accept the new version of schemas/forms directly or did you make a backup (especially doing a export package (xml file) or by copying the code into text files as backup?

In case of no backup of customized forms losts, good luck to redo your work.

Regards.
J-Serge

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

Hello Nidhiv,

It seems that this ticket is a bit correlated to your previous one:

Extension of input form into another input form in Neolane

As said in the other ticket, there are extensions for schemas but not for forms, so you must modify the factory form for a schema extended as for factory schema.

Moreover, during a postupgrade operation (upgrading towards a new build), the postupgrade log file(s) (one per instance) warn(s) about the discrepancies between the current version and new version of all objects (schemas, forms).

Actually it keeps the current version and the admin people have to choose what action to do in the Admin>Settings>Conflict management node.


You can keep the current version, accept the new one, or merge manually in order to keep what you customized and adding the new elements brought by the new version/build.
Did you accept the new version of schemas/forms directly or did you make a backup (especially doing a export package (xml file) or by copying the code into text files as backup?

In case of no backup of customized forms losts, good luck to redo your work.

Regards.
J-Serge