Importing and distributing your data from one import file into multiple objects within PIM / MAM can not be easier:
Configure your import schema, inclusive sub objects; apply transformations and keep full transparency of all your imports with an Import Staging area.
- Flexibility: All your defined PXH Exports (JSON or Excel) can be directly reimported – just use your export as a template and change some values.
- Security: You can configure for every object / relation what is allowed to be changed and what is readonly.
- Visibility: You can use an import staging area where you can optionally review and control all the changes before they finally get imported. See also all previous imports with their changes and errors.
- Control: In the review process decide for every single object / field whether to import or ignore changes from your users.
- Consistency: Offers upfront full data type validation with fast response to your importing system.
- Performance: Great performance as only relevant changes are finally pushed in multiple threads to Contentserv.
- Independent: Define your own identifier for each object (e.g., ID, External Key, any custom attribute)
- Clever: Automatically detects /resolves any dependencies:
- Full folder structures can be created with one JSON (PXH detects all dependencies)
- New Products and references / table can be created and linked with one JSON
- Even MAM Assets will be automatically downloaded and exchanged when they are changed
- Storage: Offers additional storage capabilities to import and enrich products with additional frequent changing content (like stock), which you don’t want to store in your PIM, but need in some of your interfaces.
Next to standard external import scenarios combining PXH Import with PXH Export offers multiple scenarios:
- „CS Sync“: Keep (parts of) two or more completely different Contentserv projects (PIM / MAM) automatically in sync combining PXH Export with PXH Import using just configurations.
- „Calculated rules“: Build some complex calculations using just configuration by defining the rule in a PXH Export and import the result back using PXH Import. Already implemented example scenarios:
- periodically detect and update the master picture relation based on changing criteria
- sort your references based on your product data
- calculate a global workflow based on the product and its components