Support of overwritten flag in valuetype and itemtype changes the old behavior [XR-667]

In OMN 5.10 with ticket [XR-667] Support of overwritten flag in valuetype and itemtype the previous behavior of EAI was changed.

Goal

EAI supports overwritten flag in value/item type and doesn’t always set overwritten related to the template setting, so that there is no gap between OMN overwritten functionality and EAI import/export which must be handled with extra (project specific) logic.

Values that originate from products are origin=product (default value, so not required in xml), values overridden on PEO are marked by origin=peo.

Acceptance Criteria

  • Value/item type can contain overwritten flag

Important

This is a breaking change! The behaviour is changed so that an old import xml without the origin will delete the peo values since the default to originate is product.

omn.eai.importer.pim.peo.value.default.origin=PEO

Migration Steps

Check whether you use the omn.eai.importer.pim.peo.value.default.origin parameter If yes, check if you have to adapt its value correspondingly.

Examples

  • Import a value for a peo, set the origin="PEO" attribute at the value element. → when exported the new value is displayed and marked as origin="PEO"

  • Import the same xml but this time change origin="PRODUCT" → the values will be deleted from db, on export the value is loaded from product and marked as origin="PRODUCT"

Welcome to the AI Chat!

Write a prompt to get started...