Subentity deletion on import
Purpose
When defining an import mapping, either for manual or a hot folder import, sub-entities of an item, variant or product can be marked for explicit deletion. These sub-entities will be deleted during import, if they are not part of the import file.
The configuration defining which sub-entities are deleted is part of the import mapping, and therefore can be specified in the view "Sub-entity Deletion" of the "Import" perspective in the Product 360 Desktop Client. It is also possible to specify the qualification of the sub-entities that should be deleted.
Sample use cases
Replace all price information
Requirement
The import file contains several price information for items.
All purchase prices that are not contained in the import file should be deleted from the Product 360 database.
Solution
Add a sub-entity deletion configuration, e.g. for "Purchase price" with all qualifications set to "<all>".
The import mapping then looks like this:
Replace prices of a specific supplier and price type only
Requirement
The import file contains several price information for items.
All purchase prices of supplier "X" and price type "Net list price" that are not contained in the import file should be deleted from the Product 360 database.
Solution
Add a sub-entity deletion configuration, e.g. for "Purchase price" with qualification "Supplier" set to "X", qualification "Price type" set to "Net list price" and all other qualifications set to "<all>".
The import mapping then looks like this:
Replace German and English short description - the language is part of the input file
Requirement
The import file contains short descriptions in German and English for items. The language is part of the import file.
If the import file does not contain a German or respectively an English short description, then it should be deleted from the Product 360 database.
Solution
Add a sub-entity deletion configuration for "Language-specific data" with qualification "Language" set to "German;English".
The import mapping then looks like this:
Replace German and English short description - the language is part of the import mapping
Requirement
The import file contains short descriptions in German and English for items, each in a separate in XML tags, e.g. "<shortDescriptionDE>" and "<shortDescriptionEN>".
The language is part of the import mapping, where two "Language-specific data" nodes are defined, one with language "German" and one with Language "English".
If the import file does not contain a German or respectively an English short description, then it should be deleted from the Product 360 database.
Solution
Add a sub-entity deletion configuration for "Language-specific data" with qualification "Language" set to "German;English".
Also the condition for the "Language-specific data" nodes has to be configured in order to activate sub-entity deletion for this data.
The import mapping then looks like this:
