Transform, combine and validate your data on its way into or out of Perfion.
Most PIM systems face the challenge of aligning various data sources in different formats into a single source of truth. Not only from a technical viewpoint (Excel, CSV, XML, SQL), but also from a logical viewpoint (use of different measures, different namings).
But what happens:
- if one data source gives you the product weight in kilograms in an Excel file, and another source provides the same data in pounds via an XML file?
- when you must supply output in a specific proprietary format, because a third-party system requires it?
The solution is Perfion "Actions" Mapping.
Following three process steps, Perfion allows you to overcome such data mapping challenges without the need for any third-party tools. The example below is based on ingoing data, but a similar approach applies for outbound data.
Step 1: Transform
The first step is to tell Perfion where data is coming from, and how it should be interpreted. Using Perfion's own GUI, the data source is defined and a number of rules can be applied to the data, before it is ready for the next step:
Step 2: Combine and map
Once the source data has been interpreted, Perfion allows you to combine different sources (in one-source cases, this step is simply skipped). After this, it is time to configure exactly where the aligned data should be stored inside Perfion. Also, at this point it is possible to enforce restrictions on the data by setting up simple or even complex validations:
Step 3: Import
The final step is to let the data flow into its rightful place in the database. The results can be seen immediately in Perfion, and any connected system (such as a webshop) will be up-to-date with the new data:
- Combine many data sources and import into Perfion
- Simplify mapping by “divide-and-conquer”, slicing mapping into simple chunks that can be reused
- Simple settings or advanced scripting gives you flexibility
- Better data quality because data is validated and cleansed
- Avoid the cost and complexity of third-part mapping tools