Transporting Magento 1.9.3.0 Data Files as *.csv to new Magento 1.9.3.3 generate ERRORS

[LActive]

Hi all,

a first Magento experience: 

1. A production (Live) Magento 1.9.3.0 system is runnng;

2. The developers requested a development Server, which has to be identical to the production server.

Task:

1. Installation of a new development Server (Done).

2. Install a new Magento 1.9.3.3 system. (Done)

3. Export all Data as CSV Files from the Live Server 1.9.3.0  Server with the "Data Flow Profiles".

4. Presuming the exported CSV file structure from the PROD Sever is compatible to the import data structure of the DEV Server, the exported file.CSV  is taken as source file for the import.

The following errors occur:

Starting profile execution, please wait...Warning:

Please do not close the window during importing/exporting dataStarting Mage_Dataflow_Model_Convert_Parser_Csv :: parseFound 412 rows.Starting catalog/convert_adapter_product :: parseSkip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Weine" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Spirituosen" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Spirituosen" is invalid for field "attribute_set"Skip import row, is not valid value "" for field "type"Skip import row, the value "Spirituosen" is invalid for field "attribute_set"

These Errors are issued for each Data-set.

Why is Magento not importing the un-changed exports; both are Version 1.9.3.x. Were there significant data format changes between Ver 1.9.3.0 and Ver 1.9.3.3?

Any help appreciated!

[Pronto]

You're trying to import product data, but you're lacking Attribute Set Weine on your target system.

Please note that bot Attributes and Attribute Sets are not part of product information, even though their values are. You need to make sure that they exist before executing your import.

[joykeller]

Yeah you'll need to manually set up all your attributes and categories before you try to import - or find an extension that helps you do it in bulk - but if you don't have too many, just do it manually.  Your import csv can't find the attributes or values in your spreadsheet.

[charleslou6881]

It sounds like you’re experiencing some frustrating issues with the data import! Magento’s import/export functionality can be quite particular, even between minor version updates. The attribute set mismatch errors you’re seeing might stem from custom attributes on the production server that aren’t defined on the development server. Double-check if "Weine" and "Spirituosen" attribute sets exist in the DEV environment, and if not, try importing them separately.

While you're troubleshooting, it can be helpful to step away for a bit. You could explore something different, like checking out the Jollibee Philippines menu for a change of pace. Good luck!

[micheljerr9bcf]

Magento version mismatches can be frustrating, especially when transferring data between different builds. One common issue is attribute set incompatibility—double-checking the attribute definitions in both environments might help avoid import errors. Also, ensuring that the CSV formatting aligns perfectly with Magento’s requirements can prevent unexpected failures.

By the way, I was recently reading about how online menu management plays a big role in improving customer experience, especially for restaurants. It’s interesting to see how structured data makes navigation easier for users. If you're curious, Jollibee Menu Philippines has a well-organized approach to this!

[sebt13sana2f55]

Here are a few common causes and tips to resolve them:

1. Attribute Set or Missing Attributes: Ensure the attribute sets and all custom attributes used in the old version exist in the new installation. Magento will throw errors if it can’t match them.

2. CSV Format Issues: Sometimes the exported .csv has extra commas, missing headers, or inconsistent data types. Open the file in a text editor or Excel and verify the formatting carefully.

3. Encoding Problems: Make sure the .csv file is saved with UTF-8 without BOM encoding. Magento is sensitive to file encoding and might fail silently or throw confusing errors.

4. Image Paths or Media URLs: If your products have images, ensure the  media folder contains those images, or Magento will skip them or error out.

5. Version-Specific Behavior: Though both are 1.9.x versions, small changes in import/export handling might exist. Comparing sample export files from both versions can help identify structure differences.

Recommendation:
Use Magento’s DataFlow Profiles carefully or consider using extensions like Magmi (Magento Mass Importer), which handle large data and attribute mapping more flexibly.

check out best menu

[awaisupcgmd5eb]

The Oporto menu offers a unique blend of Filipino-inspired fast food that sets it apart from typical Australian fast-food chains.https://oportomenu.com/

[tariqueabr8693]

It is like a version mismatch issue or slight schema differences—double-check column headers and encoding. Sometimes re-saving the CSV with game vault 999 apk UTF-8 helps avoid those hidden import errors.

[e75117867gb368]

Try Ambers menu

[rafaelakut179c]

It’s frustrating when Magento 1.9.3.x refuses unchanged exports between versions. Although there weren’t major format changes, minor bug fixes could cause issues. First, check the exact error messages to understand the problem, as carefully as observing a level to figure out the best strategy to win in Sprunki Game. Ensure consistent file encoding (UTF-8) and line endings. Examine the export file for rogue characters or inconsistencies using a text editor. Verify permissions and consult Magento’s logs for details. As a last resort, compare database data directly. Even small differences can trigger failures, so focus on meticulous comparisons. Good luck!