CSV files can only use used to load data that can be mapped to a consistent table type structure, hence it can handle banking type data pretty well.
Investment type data does not fit well into this. The action field must contain one of a number of predetermined standard transaction types, no other entries are accepted. The particular action type determines what fields are active, however not all fields may be required. Hence depending on the action you may have a different number of fields which will not be consistent with a fixed table structure.
It is very unusual to see a CSV file with a structure that would suit loading into Investment registers, the only ones I have seen were produced by another financial program, In that instance I used a Excel add on to create QIF files from them.
I get the issues. (I’m an ex DB techy).
Found that if you import the date amount and desc for dividend trans, you can at least batch change ‘transfer’ into the income Acct by doing it in reverse. Ie. The import allocates ‘transfer’ to a default account. After the import. (Before confirming each) Go into that default account and batch change to the income account.
At least that reduces the boring click /C&P per transaction down to just the activity and security fields.
Although Would have thought it feasible to have an import option that used the ‘activity’ as the template for fields required. Given Its easier to batch change a column in xcel to “divxfr” as the driving flag than manually click, drop down etc of every row .
Oh well..... shame.