Adding options for that could be interesting indeed, maybe even in the core module.
From a technical point of view, the problem with the 'replacing' here is that it replaces the entire mapper product.ProductImportMapper, so if 2 modules replace the same mapper, there will be a conflict.
The workaround is to introduce a empty / default mapper only for the mapping 'is_active' in the core module and 'replace' only this mapper (and the main ProductImportMapper calls this 'is_active' mapper)
Hi Markus,
Thanks for your contribution!
Adding options for that could be interesting indeed, maybe even in the core module.
From a technical point of view, the problem with the 'replacing' here is that it replaces the entire mapper product. ProductImportMa pper, so if 2 modules replace the same mapper, there will be a conflict.
The workaround is to introduce a empty / default mapper only for the mapping 'is_active' in the core module and 'replace' only this mapper (and the main ProductImportMapper calls this 'is_active' mapper)