[GNC] Struggling with Export/Import of Accounts

[Adrien Monteleone]

> On Aug 4, 2019, at 12:23 PM, Michael Hendry <hendry.michael at gmail.com> wrote:
> 
>> On 4 Aug 2019, at 16:32, Adrien Monteleone <adrien.monteleone at lusfiber.net> wrote:
>> 
>> I’ve had no issue exporting and importing an account tree myself.
>> 
>> I see you’re using a comma as part of an account name. While changing the separator and using quotes should work, I try to avoid commas in CSV data as a rule.
>> 
>> Try using something else like `-` (hyphen), `–` (en dash), `—` (em dash), `~` (tilde), or `_` (underscore) and see if that works without quotes and with the standard comma separator or CamelCase the names if that isn’t an eye sore for you.
> 
> That worked!
> 
> I restricted myself to changing one name, replacing the comma with an underscore, and edited the exported file with MacVim so as so import only that account name and all went well!
> 
> I plan now to investigate the mass-production of multiple identical transactions such as annual subscriptions by editing the CSV file in MacVim. This way I can keep the monitoring of such payments within GC, with the simple recording of the receipt of a cheque updating that individual’s account.

I would suspect a macro of vim script could handle that easily as could macros in a spreadsheet.
> 
> Many thanks,
> 
> Michael
> 
> PS My first attempt at importing the whole membership list failed, even though I’d replaced the “, “ with “_” in the account names. I had a suspicion this might relate to an e-acute (“é”) in a member’s name, and replacing this with a plain “e” worked the trick.
> 
>> 
>> Note, I’d suspect a bug, but maybe there is a good reason why it failed. Hopefully someone more familiar with the importer’s quirks will chime in.
> 
> The failure to handle UTF-8 characters looks like a bug to me.

Yep. I’d file that one. If it isn’t designed to handle them on purpose, then at least as an RFE.

Regards,
Adrien