How to Configure ISV Data Mapping
|
|
---|---|
Aim of this article | Provides a guide on mapping fields between Pricefx and Enable tables to enable regular data synchronization between the two applications. |
Related sections | https://pricefx.atlassian.net/wiki/spaces/PM/pages/5804851271 (Reference) |
Required permissions | ISV Connections - edit |
Follow these steps to create a new data mapping:
Step 1: Navigate to Data Mapping
Go to Account tab > ISV Connections > Data Mapping (requires the
ISV Connections - edit
permission).Click the Create Data Mapping button in the top-right corner.
Switch between General, Entities, Upload, Parsing, Fields, and synchronization steps and fill and save the required information.
Step 2: General
Provide the required information in the General step:
Field | Description |
---|---|
Mapping Name | A unique name for the new Data Mapping. |
Status | Choose the mapper status:
|
Direction | Choose the direction for the data flow between Pricefx and Enable.
|
Send Empty Value As | Specifies how empty values in the data should be handled during the mapping process.
|
After completing the General tab, click the Continue button to proceed to the Entities step where you define the source and target tables for mapping.
Step 3: Entities
This step defines the source and target entities for the data mapping configuration. This step establishes the entities in both Pricefx and Enable applications that will participate in the mapping process.
Field | Description |
---|---|
Pricefx Entity Type | The type of Pricefx entity (a table) that will be used as the source for data mapping when the direction Pricefx → Enable is set in the General step, or as the destination when the direction is Enable → Pricefx. |
Enable Entity Type | The type of Enable entity that will receive the mapped data when direction Pricefx → Enable is set in the General step. Currently supported Enable entities in direction Pricefx → Enable are:
Currently supported Enable entities in direction Enable → Pricefx are:
|
Enable Entity Name | The specific name of the Enable entity corresponding to the selected type (available for Dimensions and Trading partners). For example, “Products“. |
Step 4: Upload
This step allows you to upload a data file that contains the fields for the Enable entity being mapped (selected in the Entities step). This file is the basis for field mapping in the following steps and can be obtained from Enable.
File Requirements
File must include fields (columns) for the entity you are mapping.
Supported file formats and corresponding requirements:
CSV
Files that contain the BOM character are also supported.
Maximum file size: 2048 MB.
XLSX
The file has only one sheet.
The data starts in the first cell of the first column.
The first row is a header.
No macros are present in the file.
No formulas are present in the file.
Maximum file size: 20 MB.
ZIP
Preferred file encoding: UTF-8.
Uploading a File
Click the upload area to browse and select a file from your local system, or drag and drop the file into the upload area.
Once the file is uploaded successfully, you will be switched to the Parsing step.
Step 5: Parsing
This step allows you to configure how the uploaded file is interpreted by specifying parsing options such as delimiters, formatting, and special characters. This ensures the data is read and processed correctly.
Configure the parsing options for the separator, quote character, escape character, decimal separator and the date format.
If the Uploaded file contains header checkbox is selected, the first row of the file will be treated as column names.
Verify that all needed columns are present in the table (data values are not required), and click Continue to proceed to the Fields step, where the actual field mapping is configured.
Step 6: Fields
The Fields step is where the actual field mapping between Pricefx and Enable applications occurs. It allows you to map specific fields from the source to the target while applying needed conversions.
The screen displays two columns: one column lists the Pricefx entity fields, while the other column shows the fields (column names) loaded from the file uploaded in the Upload step.
Transaction date column: The field is available only when Transactions are selected in the Entities step in the Enable Entity Type field and the direction is Pricefx → Enable. Transactions require an additional column – the date of the transaction. Select the column containing the date of the transaction in the drop-down menu.
The value from the Transaction date field will be used only for the name of the export file. The transactions to be exported are still determined based on the Last Update Date.
Field Mapping
Pricefx Field
Select a field from the Pricefx entity (Pricefx table) defined earlier and adjust the data type of the field being mapped, if needed.
Enable Field
Choose the corresponding field in the Enable application where the data will be mapped. Adjust the data type of the field being mapped, if needed.
Fields that are not found are highlighted in red with a Not found in options
error. These fields require the user to manually resolve the mapping – to select the corresponding fields from the drop-down menu.
Conversion
Allows you to modify data formats or values during the mapping process.
Click Convert to open the Advanced Field Editor dialog. Here, you can configure how the data will be transformed. For example, you can use a Converter expression to convert data types (e.g., from string to date) or apply custom Groovy logic for more advanced transformations.
Once the fields are mapped and validated, you can proceed to the Synchronization step to configure and finalize data sync settings.
Step 7: Synchronization
This step enables you to define when and how often the data mapping should triggered by scheduling regular syncs.
The synchronization process checks for new data available from Enable and, if detected, initiates the mapping process to update the corresponding fields in Pricefx.
Event Time: Sets the exact date and time when the initial synchronization event will occur.
Time zone: Select the appropriate time zone for your scheduled synchronization, to ensure that the event time is interpreted correctly based on your local time settings.
Repeat: Define how frequently the synchronization should occur. Select None to set it as a non-recurring sync.
Click Create to complete the data mapping configuration and schedule the synchronization based on the specified settings.
PlatformManager version 1.75.0