[GNC] Fwd: Crash attempting to import transactions from CSV on W10

[David Carlson]

Be sure to set the date format on the import page  to match the format used
in your csv file before you try to import.  This is a known issue going
back a long time.  I thought that the current release had been modified to
address this issue, but apparently not.  I cannot check it from here.

Regarding maintenance builds, they may or may not work properly, but they
are available for testing.  Of course, try them first on disposable copies
of your data.

On Tue, Sep 1, 2020 at 9:01 PM A Harvey <gah1178 at gmail.com> wrote:

> Hi,
> I sent the forwarded message below about a dozen days ago but have received
> no comments.  I know everyone is busy and it may take some time for anyone
> to reply.  In the interim, I would like to ask two quick meta-questions if
> I may:
>
> 1) Did I send this message to the wrong list and, if so, to where should I
> send it?
>
> 2) Should I expect that the maintenance builds are likely to break parts of
> Gnucash that previously worked?
>
> Thanks,
> -Arthur
>
>
> ---------- Forwarded message ---------
> From: A Harvey <gah1178 at gmail.com>
> Date: Wed, Aug 19, 2020 at 5:01 PM
> Subject: Crash attempting to import transactions from CSV on W10
> To: gnucash-user <gnucash-user at gnucash.org>
>
>
> Hi,
> I'm getting a crash when I try to import transactions from a CSV and
> am hoping someone can help.  Here are the gory details.
>
> OS is Windows 10.
> Gnucash version gnucash-4.1-2020-08-01-git-4.1-12-g12ab85fa6+   works fine.
> All subsequent versions through ...08-15... show the following behavior:
> Upon attempting to import transactions from a CSV, the import assistant
> works correctly up to the page where it should show the results of the
> import mapping and allow certain fields to be modified.  When I click on
> NEXT to get to that page, the application crashes.
>
> I ran a trace with --debug and --extra for both the working and non-working
> versions and compared them.  Near the end of the miles of output, the
> non-working version trace file contained the following:
> .
> .
> * 16:15:16  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]  baln=0/1
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_trans_props] User
> warning: Date could not be understood.
> Value can't be parsed into a date using the selected date format.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_trans_props] User
> warning: Date could not be understood.
> Value can't be parsed into a date using the selected date format.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_split_props] User
> warning: Deposit could not be understood.
> Value doesn't appear to contain a valid number.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_trans_props] User
> warning: Date could not be understood.
> Value can't be parsed into a date using the selected date format.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_split_props] User
> warning: Deposit could not be understood.
> Value doesn't appear to contain a valid number.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_trans_props] User
> warning: Date could not be understood.
> Value can't be parsed into a date using the selected date format.
> * 16:15:58  INFO <gnc.import> [GncTxImport::update_pre_split_props] User
> warning: Deposit could not be understood.
> Value doesn't appear to contain a valid number.
> * 16:16:28  INFO <qof.engine> [qof_event_generate_internal] id=6
> hi=1345f788 han=66630812 data=00000000
> * 16:16:28  INFO <qof.engine> [qof_event_generate_internal] id=4
> hi=14016920 han=66674c38 data=00000000
> .
> .
> Any suggestions?
>
> Regards,
> -Arthur
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


-- 
David Carlson