View Issue Details

IDProjectCategoryView StatusLast Update
0000842OXID eShop (all versions)2. ----- eShop backend (admin) -----public2012-12-10 14:22
Reportermarco_steinhaeuser Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.1.1 revision 18442 
Fixed in Version4.1.2 revision 18998 
Summary0000842: Skipped fields ignored in generic import
DescriptionHere
http://www.oxid-esales.com/de/resources/forum/newbies/import-ordnet-feldernamen-nicht-richtig-zu

a user suffers from ignored skipping of fields in generic import.
To reproduce, re-name the attached file to import.csv and try to import skipping interpret, medium and label: "interpret" will be imported as "oxtitle".
Additional InformationThe behaviour is like this:
if you will select to import table file with content (to oxarticles table):
id;interpret;album;beschreibung;medium;preis;label;anzahl
1;10-96;No Retreat;punk;CD;2;;1
2;(ADV) AUDIOPHILE DATENVERARBEITUNG;S/T;lim. 5o;tape;5;Reduktive Musiken;2
3;A. LICHT / T. SHIRAISHI;Our Lips Are Sealed;;CD;10;RRR;1

... in the second step will mark assignments for fields:
id = OXARTNUM
interpret = SKIP
album = OXTITLE
beschreibung = OXLONGDESC
medium = SKIP
preis = OXPRICE
label = SKIP
anzahl = OXSTOCK
... and import the file. After import - check the imported Products:
the value from interpret is imported to OXTITLE, album to OXLONGDESC, etc..
Means the "skipped" values are imported to the next defined field, and each next field is shifted by one, what's not correct.
TagsExport, Import
Attached Files
import.jpg (227 bytes)   
import.jpg (227 bytes)   
Theme
BrowserAll
PHP Version5.2.6
Database Version5.0.33

Activities

rimvydas_paskevicius

2009-05-11 15:49

reporter   ~0000901

Fixed problem with incoret table fields mapping