Re: [GNC] Automated Reporting
On Mon, Apr 23, 2018 at 9:15 PM Sébastien de Mentenwrote: > With some python skills, you could use piecash ( > http://piecash.readthedocs.io/en/master/) to build you own reports and > export them in the best format for your needs. > We are working to support gnucash 3.0, the current version support gnucash > 2.6. > > On Mon, Apr 23, 2018, 23:26 Justin Phelps wrote: > >> I'm hoping there's a command line method for generating reports from a >> gnucash file. I want to script a series of daily, weekly, and monthly >> reports that are automatically emailed to certain people. I can achieve >> the >> scheduling and emailing from my server, but having some way to get this >> data out from gnucash without clicking through the interface would be >> really useful. >> >> How would you approach this challenge? >> > ___ >> gnucash-user mailing list >> gnucash-user@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. >> > I certainly know more Python than Scheme at this point, so the piecash tools seems promising. Does it support the XML style file, or just the SQL based solutions? ___ gnucash-user mailing list gnucash-user@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.
Re: [GNC] Automated Reporting
With some python skills, you could use piecash ( http://piecash.readthedocs.io/en/master/) to build you own reports and export them in the best format for your needs. We are working to support gnucash 3.0, the current version support gnucash 2.6. On Mon, Apr 23, 2018, 23:26 Justin Phelpswrote: > I'm hoping there's a command line method for generating reports from a > gnucash file. I want to script a series of daily, weekly, and monthly > reports that are automatically emailed to certain people. I can achieve the > scheduling and emailing from my server, but having some way to get this > data out from gnucash without clicking through the interface would be > really useful. > > How would you approach this challenge? > ___ > gnucash-user mailing list > gnucash-user@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. > ___ gnucash-user mailing list gnucash-user@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.
[GNC] Dr column mapping in CSV import bug?
Hi, dr column mapping in csv import doesn't seem to work - all figures go into credit column in transaction register after import. Regards, Peter ___ gnucash-user mailing list gnucash-user@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.
Re: [GNC] very slow upload off user data
Dear John, Thank you for your prompt reply. I have let gnucash 3.0 load my user data, and then have saved them as an XML file. Upon reopening, user data loading only took 30 seconds (instead of 30 minutes...) and the data file size has been reduced from 17Mo down to 1.7Mo. Thank you so much for your help. JF -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html ___ gnucash-user mailing list gnucash-user@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.
Re: [GNC] Automated Reporting
> On Apr 23, 2018, at 2:23 PM, Justin Phelpswrote: > > I'm hoping there's a command line method for generating reports from a > gnucash file. I want to script a series of daily, weekly, and monthly > reports that are automatically emailed to certain people. I can achieve the > scheduling and emailing from my server, but having some way to get this > data out from gnucash without clicking through the interface would be > really useful. > > How would you approach this challenge? GnuCash can be scripted in Scheme via $GNC_DATA_HOME/custom-user.scm. Since that's read and acted upon at every startup I suggest that you create a user specifically to generate the reports and and create a custom-user.scm for it and put the jobs in its crontab (or use it to create the Scheduled Action scripts if you're on Windows). Regards, John Ralls ___ gnucash-user mailing list gnucash-user@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.
[GNC] Automated Reporting
I'm hoping there's a command line method for generating reports from a gnucash file. I want to script a series of daily, weekly, and monthly reports that are automatically emailed to certain people. I can achieve the scheduling and emailing from my server, but having some way to get this data out from gnucash without clicking through the interface would be really useful. How would you approach this challenge? ___ gnucash-user mailing list gnucash-user@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.
Re: [GNC] Crash on start up
Thank you! > On 23 April 2018 at 15:11 John Rallswrote: > > > > > > On Apr 23, 2018, at 5:40 AM, Samantha Payn wrote: > > > > I am running GNUcash 3 on Windows 10. seem to have done something to > > corrupt my experimental GNUcash accounts file. It crashes on start-up. > > I have tried uninstalling and reinstalling GNUcash but that hasn't > > helped. > > > > Once it has crashed I get the locked file warning, and whether I choose > > "open anyway" or "open as read only" the file crashes. I am able to > > open the app only by clicking on "create new file". > > > > I am able to open an earlier version of the damaged file but would like > > to know how I have caused this problem. > > > > The initial Trace File after the first crash says: > > > > "* 07:12:40 CRIT gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > * 07:14:21 CRIT gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > * 07:15:49 WARN [gnc_print_time64()] Error processing > > time64 9223372036854775807: Time value is outside the supported year > > range. > > * 07:17:17 WARN [gnc_print_time64()] Error processing > > time64 9223372036854775807: Time value is outside the supported year > > range. > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:17:40 WARN invalid uninstantiatable type '(NULL)' > > in cast to 'QofInstance' > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:17:40 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > > * 07:21:30 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:23:52 CRIT gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > * 07:34:34 CRIT gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > * 07:36:35 CRIT gnc_date_edit_set_time_internal: assertion > > 'mytm != NULL' failed > > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:37:19 CRIT [gnc_price_get_value()] price NULL. > > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:38:14 CRIT [gnc_price_get_value()] price NULL. > > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:38:32 WARN [gnc_numeric_to_decimal()] Rounding required > > when 'never round' specified. > > * 07:42:10 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:42:10 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:42:10 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the supported year > > range. > > * 07:42:10 WARN [qof_print_date_buff()] Error processing > > time64 527765583310712933: Time value is outside the
Re: [GNC] Crash on start up
> On Apr 23, 2018, at 5:40 AM, Samantha Payn> wrote: > > I am running GNUcash 3 on Windows 10. seem to have done something to > corrupt my experimental GNUcash accounts file. It crashes on start-up. > I have tried uninstalling and reinstalling GNUcash but that hasn't > helped. > > Once it has crashed I get the locked file warning, and whether I choose > "open anyway" or "open as read only" the file crashes. I am able to > open the app only by clicking on "create new file". > > I am able to open an earlier version of the damaged file but would like > to know how I have caused this problem. > > The initial Trace File after the first crash says: > > "* 07:12:40 CRIT gnc_date_edit_set_time_internal: assertion > 'mytm != NULL' failed > * 07:14:21 CRIT gnc_date_edit_set_time_internal: assertion > 'mytm != NULL' failed > * 07:15:49 WARN [gnc_print_time64()] Error processing > time64 9223372036854775807: Time value is outside the supported year > range. > * 07:17:17 WARN [gnc_print_time64()] Error processing > time64 9223372036854775807: Time value is outside the supported year > range. > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:17:40 WARN invalid uninstantiatable type '(NULL)' > in cast to 'QofInstance' > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:17:40 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:17 CRIT [gnc_price_get_value()] price NULL. > * 07:21:30 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:23:52 CRIT gnc_date_edit_set_time_internal: assertion > 'mytm != NULL' failed > * 07:34:34 CRIT gnc_date_edit_set_time_internal: assertion > 'mytm != NULL' failed > * 07:36:35 CRIT gnc_date_edit_set_time_internal: assertion > 'mytm != NULL' failed > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:37:19 CRIT [gnc_price_get_value()] price NULL. > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:37:19 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:38:14 CRIT [gnc_price_get_value()] price NULL. > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:38:14 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:38:32 WARN [gnc_numeric_to_decimal()] Rounding required > when 'never round' specified. > * 07:42:10 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:42:10 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:42:10 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:42:10 WARN [qof_print_date_buff()] Error processing > time64 527765583310712933: Time value is outside the supported year > range. > * 07:42:10 WARN invalid cast from '(NULL)' to > 'QofInstance'" > > After that all the trace files say the same thing (apart from the > timestamp): > > "* 07:42:44 WARN invalid uninstantiatable type '(NULL)' > in cast to 'QofInstance'" > Thanks for any help anyone can give. You have a pile of invalid dates in your data file. GnuCash 2.6.x had a broader allowable date range