I have been experimenting with the export and import of accounts of the form: Assets:Current Assets:Members:Surname_Forename I was successful when I edited the export file down to a single account, but failed when I tried to import all of the members' accounts. One of our members has an e-acute ("é") in his forename, and I suspected this might be the issue. Changing the e-acute to an ASCII lowercase "e" solved the problem.
I tested this problem with current master (~3.10+). I had to use a different format from above as now CSV importer says you must use same format as exported. Not sure when this started. Here is the format that worked: (Using UTF-8) type, full_name,name,code,description,color,notes,commoditym,commodityn,hidden,tax,placeholder ASSET,Assets:Current Assets:Members:Surname_Forename1,Surname_Forename1,,Surname_Forename1,,,AUD,CURRENCY,F,F,F ASSET,Assets:Current Assets:Members:Surname_Forenamé2,Surname_Forenamé2,,Surname_Forenamé2,,,AUD,CURRENCY,F,F,F ASSET,Assets:Current Assets:Members:Surname_Forename3,Surname_Forename3,,Surname_Forename3,,,AUD,CURRENCY,F,F,F Note 2nd data record (Surname_Forenamé2) has "é" in full_name, name and description. If I didn't use "é" in full_name, but did in name, the record did not import, presumably because of mismatch between fullname + name. Please try with the format as above?
This seems similar to Bug 797088 where it works in Linux but not in Mac OS.
My testing re comment 1 was in Linux.
*** This bug has been marked as a duplicate of bug 797088 ***
