Good Practice? Where do you manage programmatical CMS-Impex updates

[mwoelm]

Hi,

during project initiation we create our CMS content with the impex files in the appropriate project data paths.

When we deploy on a stage or prod system, we want to avoid reinitialization of the system. Therefore, after this time, we do not know where to put IMPEX files which change Catalog aware data and work even during update as well as during init.

• Essential data? Of course no.

• Project data? Maybe, but project data should only be executed once, so it is nothing for "patching catalog aware content".

• Patch? We`ve tried that, but it seems that during an initialization the patch impexes are executed too early. So the Catalog aware impexs are failing.

How do you guys manage your Catalog aware changes in impex files?

It seems there`s no way to create those content twice, in a seperate migration file and in the appropriate file below project data for initialization.

Best Regards Michael

[geffchang]

I'm not sure about best practice, but I think it's fine to put it in project data. You can use a boolean user-defined parameter, so that you can decide during Platform Update if you want to import an impex or not.

See "Usage of User-Defined Parameters" in https://help.sap.com/viewer/d0224eca81e249cb821f2cdf45a82ace/6.6.0.0/en-US/8bcb3edb86691014af58b7162...