Introduction to data transformation
Transforming data means changing its format to the one you need. The transformation of data can be performed in the Automation module on a sample file. With a library of nodes you can modify the file by adding, renaming, and merging columns as well as editing the values in the rows, and so on.
You can learn more how to build a data transformation here.
Further use of transformation
Imports
After the data transformation is published, you can use it in the Data Transformation node while preparing a workflow that imports the files.
If your file meets the Synerise import requirements, you can omit the data transformation part.
Example import workflow
With transformation
When to use
If the files you want to import to Synerise don’t meet the requirements, you can create a data transformation and use it in the Data Transformation node.
Workflow structure
- Scheduled run node - This node allows you to define the frequency of importing the file.
- Local File node - This node allows you to upload a file from your device to be modified. You can also upload data through SFTP or HTTP.
- Data Transformation node - This node allows you to prepare your file to meet Synerise requirements.
- Import nodes - The scope of the nodes include: Import customers, Import transactions, Import events, Import to catalog. These nodes don’t require configuration, they list the requirements for the files to be imported.
- The End node.
Without transformation
When to use
If the file you want to import to Synerise meets the requirements, you don’t need to use the Data Transformation node.
Workflow structure
- Scheduled run node - This node allows you to define the frequency of importing the file.
- Local File node - This node allows you to upload a file from your device. You can also upload data through SFTP or HTTP.
- Import nodes - The scope of the nodes include: Import customers, Import transactions, Import events, Import to catalog. These nodes don’t require configuration, they list the requirements for the files to be imported.
- The End node.
Import requirements
The file after the transformation must include the following columns:
firstNamelastNameemail
The file after the transformation must include the following columns:
actionlabeltype- if you import events other thancustom, fill in the type of the event according to the API documentation.
The file after the transformation must include the following columns:
orderIdpaymentInfo.methodproducts.finalUnitPrice.amountproducts.finalUnitPrice.currencyproducts.nameproducts.quantityproducts.skurevenue.amountrevenue.currencyvalue.amountvalue.currency
Create a catalog to which you will import data.
Import nodes explanation
Import customers
This node allows you to initiate an import of customers to Synerise. The node doesn’t require any configuration. Its purpose is only to categorize the file provided by the preceding Get File node.
Click here to learn more.
Import transactions
This node allows you to initiate an import of transactions to Synerise. The node doesn’t require any configuration. Its purpose is only to categorize the file provided by the preceding Get File node.
Click here to learn more.
Import events
This node allows you to initiate an import of events to Synerise. The node doesn’t require any configuration. Its purpose is only to categorize the file provided by the preceding Get File node.
Click here to learn more.
Import to catalogs
This node initiates the import of data to a catalog created in Data Management > Catalogs. The catalog can be empty.
In the configuration of the node:
- Select the catalog to which the file will be imported.
- As the primary key, enter the name of the column which contains the unique identifiers of the items.
- Confirm by clicking Apply.
Click here to learn more.
