Complete Guide: Import Yes/No CSV in Magento 2.4.8-p3

To import Yes/No custom attributes from CSV in Magento 2.4.8-p3, you must use “1” for true and “0” for false in your CSV file, ensure proper column mapping, and configure the attribute correctly. The key is to use numeric boolean values (1/0) rather than text values (Yes/No), and to handle the attribute either in its own dedicated column or properly within the additional_attributes column.

Contents

• Correct CSV Format for Boolean Values
• Column Mapping and Header Configuration
• Individual Columns vs Additional_attributes
• Attribute Configuration Requirements
• Troubleshooting Common Issues
• Backend and Frontend Filtering
• Integration with Promotions and Cart Rules

Correct CSV Format for Boolean Values

The most critical aspect of importing boolean attributes in Magento 2 is using the correct value format. Based on the research findings, Magento requires numeric values for boolean attributes:

• Use “1” to represent Yes (true)
• Use “0” to represent No (false)

Important: Do not use text values like “Yes”, “No”, “yes”, “no”, or any quoted variations. These will not be recognized by the import system.

sku,upgrade_eligible
PRODUCT001,1
PRODUCT002,0
PRODUCT003,1

The Stack Overflow discussion confirms this approach: “To import boolean value, you have tu use ‘1’ for true and ‘0’ for false in your CSV file. But, ensure the column is correctly mapped to the corresponding attribute in Magento.”

Column Mapping and Header Configuration

Proper column mapping is essential for successful imports. There are two main approaches:

Individual Column Approach

1. Create a dedicated column in your CSV with the exact attribute code as the header
2. Use the numeric values (1/0) in this column
3. Ensure the column header matches the attribute code exactly (case-sensitive)

sku,name,price,upgrade_eligible
PRODUCT001,Product Name,19.99,1

Additional_attributes Approach

For custom attributes, you can also include them in the additional_attributes column:

sku,additional_attributes
PRODUCT001,"upgrade_eligible=1"
PRODUCT002,"upgrade_eligible=0"

According to the Magento Stack Exchange discussion, you need to fill all custom attributes into the single column named additional_attributes_code.

Individual Columns vs Additional_attributes

Each approach has its advantages:

Individual Columns:

• Better for bulk updates of specific attributes
• Easier to read and maintain
• Better performance for large imports
• Recommended for boolean attributes based on research findings

Additional_attributes:

• Useful for updating multiple attributes at once
• More compact CSV format
• Can be problematic for boolean values in some Magento versions

The GitHub issue indicates that “Import CSV files to update product boolean attribute does not work if the attribute is present on ‘additional_attributes’.” This suggests that individual columns are more reliable for boolean attributes.

Attribute Configuration Requirements

For your ‘upgrade_eligible’ attribute to work properly:

1. Attribute Type: Keep it as “Yes/No” - do not change to Dropdown or MultiSelect
2. Scope: Set to appropriate scope (Global, Website, or Store)
3. Default Value: Configure if needed
4. Unique Values: Set based on your requirements
5. Required: Set based on your business logic

The Amit Bera’s guide provides detailed steps for creating Yes/No product attributes, though the focus is on programmatic creation rather than CSV import.

Troubleshooting Common Issues

If you’re still experiencing issues:

Value Format Issues

• Problem: Using “Yes”/“No” instead of “1”/“0”
• Solution: Convert all boolean values to numeric format
• Verification: Check exported CSV to see the actual format Magento uses

Column Header Issues

• Problem: Incorrect attribute code in column header
• Solution: Export a sample product to see the exact column name
• Note: Column headers are case-sensitive

Mapping Issues

• Problem: Attribute not properly mapped during import
• Solution: Use the “Check Data” step before final import
• Tip: Start with a small test file (2-3 products) before full import

The BSSCommerce documentation states: “For columns with values as 0 or 1: if you enter the wrong value, the system will change into default value as 0.”

Backend and Frontend Filtering

Once successfully imported, your boolean attribute should work for filtering:

Backend Filtering

• Go to Catalog > Products
• Use the Filters panel
• Select your ‘upgrade_eligible’ attribute
• Filter by “Yes” or “No” values

Frontend Filtering

• Ensure the attribute is set as “Filterable (with results)” in the attribute configuration
• Clear the cache after making changes
• Test the filter on the frontend

The filtering functionality should work seamlessly once the attribute values are properly imported as 1/0.

Integration with Promotions and Cart Rules

For using your boolean attribute in promotions and cart rules:

1. Cart Conditions: Add conditions based on the attribute value

   • “If ALL of these conditions are TRUE:”
   • “Attribute Set” = Your Attribute Set
   • “upgrade_eligible” = “Yes”

2. Promotion Actions: Apply discounts based on the attribute

   • Shopping Cart Price Rule conditions can reference the attribute
   • Catalog Price Rule conditions work similarly

3. Verification: Test the rules with products that have different attribute values to ensure they’re being recognized correctly.

Conclusion

To successfully import Yes/No custom attributes in Magento 2.4.8-p3:

1. Always use “1” for Yes and “0” for No - this is the only format that works reliably
2. Use individual columns rather than including boolean attributes in additional_attributes
3. Ensure exact column header matching with the attribute code (case-sensitive)
4. Keep the attribute as Yes/No type - don’t change to Dropdown or MultiSelect
5. Test with small files first before attempting large imports

The key insight is that Magento’s import system expects numeric representation of boolean values, not text representations. This explains why your manual exports work (Magento converts Yes to 1 internally) but your imports with text values fail.

If you continue to experience issues, consider exporting a sample product to see exactly how Magento represents the attribute in the export file, then match that format precisely in your import file.

Sources

1. Magento Yes/No Import from CSV Issue - Stack Overflow
2. Product custom attribute import with CSV Magento 2 - Magento Stack Exchange
3. User Guide - Magento 2 Import Export Product Attributes Extension
4. Can’t import additional_attributes 2.4.3 · GitHub Issue
5. Magento 2 Export Product Attributes Conflicts - MGT Commerce