Attributes
Pacemaker Import Community provides the command import:attributes
command for the attribute import.
- The individual parts of the file name must match the pattern as followed:
attribute-import_20190608-114344_01.csv
<IMPORT-DIRECTORY>/<PREFIX>_<FILENAME>_<COUNTER>.<SUFFIX>
- <IMPORT-DIRECTORY>:
-
is by default the loation of your working directory
<ROOT-DIRECTORY>/var/pacemaker/import/
-
The
var/pacemaker/import
directory is not created after the installation by default
-
- PREFIX:
-
The
<PREFIX>
of the import filename represents theattribute-import
area. - DELIMITER (
_
): -
The mandatory Delimiter (
_
) for the import filename between<PREFIX>
and<FILENAME>
is a underscore (_
). - FILENAME:
-
The filename is a autogenerated combination of date and time.
-
As a result, the filename look like
attribute-import_20190608-114344_01.csv
.
-
- DELIMITER (
_
): -
The mandatory Delimiter (
_
) for the structured filename between<FILENAME>
and<COUNTER>
is underscore (_
). - COUNTER:
-
is a incremental number with two digits starting with
01
. - SUFFIX (filename extension):
-
The Pacemaker Import Community uses the
<SUFFIX>
.csv
as default for the import files.
.OK file:
Bunch import:
|
Your CSV file var/pacemaker/import/attribute-import_20190608-114344_01.csv
is now ready for import.
Unique identifier
-
The unique identifier for the attribute import is the attribute code
-
The attribute code is a mandatory field available in the column
attribute_code
on every row of the CSV file
Columns
- The CSV file with the attributes for Magento 2 CE/EE consists of the following columns
Column Name | Type | Example | Description |
---|---|---|---|
|
|
The specific store view(s) for attribute translations
|
|
|
|
Assigning the attribute to a specific attribute set |
|
|
|
Assigning the attribute to a specific attribute group |
|
|
|
The entity type code, a attribute is bound to |
|
|
|
The unique attribue code |
|
|
|
The attributes sort order in the backend/frontend |
|
|
|
A comma (,) separated list with the attribute options and their values |
|
|
|
A pipe (|) separated list with the attribute option swatch configuration (see additional_data column) |
|
|
|
The attribute options sort order in the backend/frontend |
|
|
|
The model to load the EAV data from
|
|
|
|
The model to convert the user input
|
|
|
|
The table to store the user input |
|
|
|
The model to validate the user input
|
|
|
|
The frontend input type
|
|
|
|
The attribute label in the admin store |
|
|
|
A CSS class name |
|
|
|
The model to load the available values
|
|
|
|
Frontend input renderer
|
|
|
|
A comma (,) separated list with product types the attribute applies to |
|
|
|
The attributes backend type
|
|
|
|
The attribute value is mandatory |
|
|
|
Custom user defined attribute |
|
|
|
The default value of the attribute
|
|
|
|
The attribute must contain a unique value in the configured context |
|
|
|
Custom attribute note
|
|
|
|
The attribute is global and can be used to create configurable products |
|
|
|
The attribute is visible in the backend |
|
|
|
The attribute gets set searchable in frontend |
|
|
|
The attribute is available in the filter navigation |
|
|
|
The attribute is usable in product comparison |
|
|
|
The attribute is visible on the catalog pages in a storefront |
|
|
|
The attribute value allows us to contain HTML code in a storefront |
|
|
|
The attribute can be used to create catalog price rules |
|
|
|
The attribute values can be used to filter the search results |
|
|
|
The attribute values will be rendered in the catalog |
|
|
|
The attribute values can be used to sort the catalog |
|
|
|
The attribute is visible in the advanced search |
|
|
|
Position of the attribute in the layered navigation block |
|
|
|
The WYSIWYG editor must get enabled to edit the attribute’s value |
|
|
|
The attribute can be used to create promo rules |
|
|
|
The attribute must have a value in the admin store |
|
|
|
Is used in the grid |
|
|
|
Is visible in the grid |
|
|
|
Is filterable in the grid |
|
|
|
Search weight |
|
|
|
A comma (
|
|