This all started with defect 145117 which I was told was fixed in the latest release. It seems to me that it is not fixed, although the nature of the defect has changed, but so far I have not convinced my rep that its still a defect.
The problem,now, is that in a CSV transaction (orders) import using 2 files the Item field does not simply map to the Item/Name Number field. Instead, to get the import to work I would need to map the Item field to a merger of several fields.
The purported workaround is to map item to (item parent if any) + Item/Name Number field + Display Name/Code.
For example, if I have a matrix item with a parent Item/Name called "SKU1" and a child called "SKU1B" and the child has a Display Name/Code of "Fun Item" then I would have to map the Item field in the import to "SKU1 - SKU1B Fun Item"
I cant imagine the programmers intended this crazy mapping as there is no reason to use it over just plain mapping Item to Item so I would only have to (using the last example) map Item to "SKU1B".
At best, this remaping is a possible work around but it does not work for me because I change the Display Name Code over time, and the source of the data I am using has a character limit that would prevent me from putting in the full mapping.
So the result is that I cant use CSV import to import transactions. I cant imagine anyone could except in rare and limited cases (like they dont use Display Name at all in the item record).
Yet- I can't get this treated as an issue and my rep just wants to close it.
Any ideas? The current case is 782047