IMPORT.FEATUREDATA
IMPORT.FEATUREDATA was introduced in Perfion 5.5 2024-R2. It takes Input from a Excel file or the Table-format and imports it into any base feature.
Properties
From | The Path to excel file. |
To | The name of the feature to import data to (e.g. Product, Category etc.) NOTE: The destination can also be assigned dynamically from the content of a variable, e.g. by writing {=$MyVariableName}. |
Parameters
All parameters are optional, but can be defined to alter the default behavior of the import.
@KeyFeatureColumn | Column in excel file or input data source containing values to be used as import keys. The key feature column can be located anywhere in the input data source. Key Feature Requirements:
Base feature exception: The base feature (= the feature to import to) can naturally also be used as key feature. This feature will always be selectable as it holds the items you want to update. The base feature can also be inheritable and allow multiple, and it data types Image, File and Date are also supported. Possible values:
NOTE: if the parameter @KeyFeatureColumn is not specified, the importer will use the first non-excluded column as key. |
@NewItemHandling | By default, new items in the input data source are created in Perfion.
|
@EmptyCellHandling | By default, the importer ignores empty cells in the input data source Possible values:
NOTE: If a cell in the input data source contains the value [DeleteValues], the importer will delete the existing value in Perfion for that particular cell even if KeepValues is used. |
@MultiValueHandling | By default, the importer will merge values in input data source with existing values in Perfion for multivalue features. Possible values:
|
@UnknownSelectableValueHandling | By default, the importer will create new selectable items in Perfion when unknown selectable values are found in input data source. Possible values:
|
@ValidationViolationHandling | By default, the importer will fail and throw an error if values in input data source violate “hard” validation rules on features. Possible values:
NOTE: “Soft” validation rules are not respected by the importer. Values that violate soft validation rules will always be imported. |
@DateFormat | By default, the importer will accept and understand dates from Excel without specifying a specific format. If dates are imported from other systems - or imported to multivalue date features - you must specify the date format found in the input data source. Possible values:
|
@DecimalSeparator | By default, the importer will accept and understand numbers from Excel without specifying a decimal separator. If numbers are imported from other systems - or imported to multivalue number features - you must specify the decimal separtor found in the input data source. Possible values:
NOTE: When specifying a decimal separator, you must also specify a group separator |
@GroupSeparator | By default, the importer will accept and understand numbers from Excel without specifying a group separator. If numbers are imported from other systems - or imported to multivalue number features - you must specify the group separtor found in the input data source. Possible values:
NOTE: When specifying a group separator, you must also specify a decimal separator |
@ZippedBinariesFile | The Path to a zip file for importing binary files. NOTE: Binary files will be imported from zip file when file references in input data source do not include paths (e.g. image1.jpg) |
@EmptyDataTableHandling | By default, the importer will ignore empty input data sources as long as column headers are valid. Possible values:
|
@OperationMode | By default, the importer will validate column headers and data AND import the data. Possible values:
NOTE: ValidateOnly will usually take the same time to run as Normal. This is because the importer still goes through all import steps but then roll back the entire transaction at the end. |
Map
This Command does not use any value mappings.
- 1 Properties
- 2 Parameters
- 3 Map