Everyone, Should I open a bug report? I would think that looking at an incorrect register would be deemed a bug and not a feature request.
On Sun, Oct 3, 2021 at 8:03 PM Christina Martin <[email protected]> wrote: > I agree Glenn. It used to do so. > > Regards, > Christina > > *Christina Martin* > Sent from my device, please excuse any typo's. > > On 4 October 2021 1:27:12 am Glenn Fowler <[email protected]> wrote: > >> Hi Christina, >> >> What you described is the same issue. The only difference is I am >> pressing <enter> and you are closing and reopening the register for the >> scheduled transactions to appear. >> >> The expected behaviour should be for the scheduled transactions to appear >> without user input in the register. >> >> On Sat, Oct 2, 2021 at 10:17 PM Christina Martin < >> [email protected]> wrote: >> >>> I have a similar problem, although I haven't tried entering a blank txn. >>> Another user reported something similar back in February and I tried to >>> add >>> my $0.02 worth at the time, but two messages I sent didn't get through. >>> >>> In a nutshell, I save the registry, close and reopen it and the txns >>> show up. >>> >>> Below is a copy of the information I tried to send in Feb, setting out >>> the >>> testing I had done. >>> >>> "I tried to send this response to the list 2 days ago, but I haven't >>> seen >>> it come in on the digest, so I must have done something wrong. >>> >>> >>> >>> >>> I finally had time to sit down and do some testing and I'm covering >>> things >>> raised and suggested in a variety of digests up to Wed 10/2. >>> >>> >>> >>> >>> This odd behaviour started when I was using the previous version, and I >>> hoped that the upgrade to the 4.x series would fix it. I *think* I was >>> still on 2.x when I upgraded last year, but I can't be certain of that >>> (the >>> manual update process means I tend to leave it for a while). For a >>> variety >>> of reasons that I don't wish to get into now, I decided to start a new >>> file >>> for the start of the Australian financial year on 1 July 2020. I can't >>> remember exactly what I did except that it involved a blank copy of the >>> original account tree. I then manually created all my scheduled >>> transactions to match the original file. I don't know if that means that >>> I've somehow imported an old error. >>> >>> >>> >>> >>> I'm running GC 4.2 (build 4.2+(2020-09-26) on Windows 10 Home 64 bit OS >>> (build 19041.746). The only filters I have set are to hide reconciled >>> txns >>> in each register, and the financial year for Australia. >>> >>> >>> >>> >>> The first thing I've noticed is that I don't need to fully close GC to >>> get >>> the scheduled txns to display - closing and reopening the account is >>> sufficient. I tend to keep all 4 personal accounts open all the time >>> inside >>> GC, so I guess I'd potentially have to close and reopen all 4, in which >>> case, closing and reopening the entire file is easier. >>> >>> >>> >>> >>> I have created a new scheduled txn from a dummy txn in my register. I >>> left >>> "Notify me when created ticked". I saved the file and then ran Actions >>> -> >>> Scheduled Txns -> Since Last Run... I cancelled the Since Last Run >>> window >>> that popped up. The txns did not display until I closed and reopened the >>> account register although I could see that the balance in the register >>> changed where the next txn should be showing up. When I click on OK at >>> the >>> Since Last Run window, the full details of the scheduled txns >>> immediately >>> show up in the register. If I click on the "Review Created Transactions" >>> check box in the Since Last Run... window and click on OK, the two txns >>> that should show up open in a new register window titled Created >>> Transactions *and* I can see them immediately in the account register. >>> >>> >>> >>> >>> David Carlson mentioned that he didn't know what I meant by GC telling >>> me >>> on start up how many scheduled txns it had created. My scheduled txns >>> are >>> *always* set to be Enabled (ticked) Create automatically (ticked) Create >>> in >>> advance 14 days ticked. I always disable Notify me when created (as I >>> hadn't noticed until today that was an option to turn off in Edit -> >>> Preferences -> Scheduled Transactions - in my defence, I last edited >>> them >>> several years ago). I created a new scheduled txn according to these >>> parameters and I get a pop-up window on start up that says: >>> >>> >>> >>> >>> "There are no Scheduled Transactions to be entered at this time. (2 >>> transactions automatically created) -> Close" >>> >>> >>> >>> >>> The txns will change the balance in the register, but the actual detail >>> won't display until the account is closed and reopened. >>> >>> >>> >>> >>> If I have "Notify me when created" checked, I get the Since Last Run >>> window >>> instead. All of my 30+ scheduled txns do *not* have this enabled - I do >>> not >>> need to be told what they are on start up, I just need them to show up >>> in >>> the register - and I have run it this way since very early on in using >>> GC, >>> it must be at least 10 years. The problem I'm seeing started some time >>> in >>> 2019 (or at the very latest, very early 2020). I'm vague about exactly >>> when >>> because it took a while to be certain I was seeing a consistent issue >>> and >>> not imagining it (since they eventually displayed). >>> >>> >>> >>> >>> The last thing I tried was to turn off "Notify before transactions are >>> created" in Edit -> Preferences -> Scheduled Transactions. I then went >>> through the steps of creating and running a new scheduled txn only to >>> find >>> the same problem that the register balance changes, but the detail >>> doesn't >>> display until the account is closed and reopened. >>> >>> >>> >>> >>> It definitely seems that whether or not the Notification is set to show >>> or >>> not is key to the issue, but I have to reiterate that I didn't change >>> how I >>> handled my scheduled txns when I first started seeing it. I'm not sure >>> what >>> the next step here is." >>> >>> >>> Regards, >>> Christina >>> >>> Christina Martin >>> Sent from my device, please excuse any typo's. >>> >>> >>> On 3 October 2021 11:23:42 am [email protected] wrote: >>> >>> > Send gnucash-user mailing list submissions to >>> > [email protected] >>> > >>> > To subscribe or unsubscribe via the World Wide Web, visit >>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user >>> > or, via email, send a message with subject or body 'help' to >>> > [email protected] >>> > >>> > You can reach the person managing the list at >>> > [email protected] >>> > >>> > When replying, please edit your Subject line so it is more specific >>> > than "Re: Contents of gnucash-user digest..." >>> > >>> > >>> > Today's Topics: >>> > >>> > 1. Re: Making the leap to latest (Derek Atkins) >>> > 2. Re: Making the leap to latest (AC) >>> > 3. Re: Making the leap to latest (AC) >>> > 4. Re: Making the leap to latest (Derek Atkins) >>> > 5. Re: Making the leap to latest (Derek Atkins) >>> > 6. Re: Making the leap to latest (Michael or Penny Novack) >>> > 7. Re: Scheduled transactions do not appear in the register >>> > until <enter> is pressed (Robin Chattopadhyay) >>> > 8. Re: Scheduled transactions do not appear in the register >>> > until <enter> is pressed (Glenn Fowler) >>> > 9. Re: OFX Import with Investment Transactions (Robin Chattopadhyay) >>> > >>> > >>> > ---------------------------------------------------------------------- >>> > >>> > Message: 1 >>> > Date: Sat, 02 Oct 2021 18:06:40 -0400 >>> > From: Derek Atkins <[email protected]> >>> > To: AC <[email protected]>, GnuCash users group >>> > <[email protected]> >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: >>> > <[email protected]> >>> > Content-Type: text/plain; format=flowed; charset="us-ascii" >>> > >>> >> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >>> > >>> > At every version you should load your data file and then save it. >>> > >>> > While there is no requirement to upgrade, and "if it ain't broke, >>> don't fix >>> > it" may apply, if you have a system crash and need to rebuild your >>> system, >>> > it'll be easier to use recent versions. >>> > >>> > -derek >>> > Sent using my mobile device. Please excuse any typos. >>> > On October 2, 2021 5:56:23 PM AC <[email protected]> wrote: >>> > >>> >> Ok, I've been running along on 2.6.3 on Win 10. No issues to date >>> that >>> >> I can see. >>> >> >>> >> I know there's been various changes throughout the rest of the 2.x and >>> >> 3.x series and we're now on 4.x which sparks some questions: >>> >> >>> >> >>> >> Do I really need to update? I only use the basis ledgers for standard >>> >> banking accounts, credit cards, loans, mutual funds; scheduled >>> >> transactions; and basic reports (typically just the standard >>> transaction >>> >> report when I need a list for taxes). I don't use online transactions, >>> >> imports, or business features. Can I assume that the basics still >>> work >>> >> the same way? >>> >> >>> >> If it's better for me to go ahead and update how painful will it be to >>> >> update? >>> >> >>> >> I recall some suggestions previously about upgrading in increments and >>> >> if that's the case how many increments am I going to need (hopefully >>> not >>> >> one for every point version)? >>> >> >>> >> _______________________________________________ >>> >> gnucash-user mailing list >>> >> [email protected] >>> >> 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. >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 2 >>> > Date: Sat, 2 Oct 2021 15:11:39 -0700 >>> > From: AC <[email protected]> >>> > To: Derek Atkins <[email protected]>, GnuCash users group >>> > <[email protected]> >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: <[email protected]> >>> > Content-Type: text/plain; charset=windows-1252 >>> > >>> > I agree don't upgrade if not absolutely necessary but I will likely be >>> > replacing this computer in a few months so starting from a newer >>> > installation is much more likely to happen in that case. >>> > >>> > So you're saying I should be able to do three stages of 2.6.last, >>> > 3.x.last and then 4.x.last? >>> > >>> > Are there any big changes to basic functionality from 2.6 to 4.x? I'm >>> > making my way through the change logs but a lot of it is related to >>> > various features I don't use (at least that which I've read thus far). >>> > >>> > >>> > On 2021-10-02 15:06, Derek Atkins wrote: >>> >>> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >>> >> >>> >> At every version you should load your data file and then save it. >>> >> >>> >> While there is no requirement to upgrade, and "if it ain't broke, >>> don't >>> >> fix it" may apply, if you have a system crash and need to rebuild your >>> >> system, it'll be easier to use recent versions. >>> >> >>> >> -derek >>> >> Sent using my mobile device. Please excuse any typos. >>> >> On October 2, 2021 5:56:23 PM AC <[email protected]> wrote: >>> >> >>> >>> Ok, I've been running along on 2.6.3 on Win 10.? No issues to date >>> that >>> >>> I can see. >>> >>> >>> >>> I know there's been various changes throughout the rest of the 2.x >>> and >>> >>> 3.x series and we're now on 4.x which sparks some questions: >>> >>> >>> >>> >>> >>> Do I really need to update?? I only use the basis ledgers for >>> standard >>> >>> banking accounts, credit cards, loans, mutual funds; scheduled >>> >>> transactions; and basic reports (typically just the standard >>> transaction >>> >>> report when I need a list for taxes). I don't use online >>> transactions, >>> >>> imports, or business features.? Can I assume that the basics still >>> work >>> >>> the same way? >>> >>> >>> >>> If it's better for me to go ahead and update how painful will it be >>> to >>> >>> update? >>> >>> >>> >>> I recall some suggestions previously about upgrading in increments >>> and >>> >>> if that's the case how many increments am I going to need (hopefully >>> not >>> >>> one for every point version)? >>> >>> >>> >>> _______________________________________________ >>> >>> gnucash-user mailing list >>> >>> [email protected] >>> >>> 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. >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 3 >>> > Date: Sat, 2 Oct 2021 15:18:19 -0700 >>> > From: AC <[email protected]> >>> > To: [email protected] >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: <[email protected]> >>> > Content-Type: text/plain; charset=windows-1252 >>> > >>> > Actually, related to this: Is there a straightforward way to try a >>> > version without having to go through a complete installation on Windows >>> > and without disturbing the existing installation? >>> > >>> > If it's possible then I could run 2.6.last and then 3.x stand-alone >>> with >>> > a test copy of the file before jumping to 4.x and committing to the >>> full >>> > install. >>> > >>> > On 2021-10-02 15:11, AC wrote: >>> >> I agree don't upgrade if not absolutely necessary but I will likely be >>> >> replacing this computer in a few months so starting from a newer >>> >> installation is much more likely to happen in that case. >>> >> >>> >> So you're saying I should be able to do three stages of 2.6.last, >>> >> 3.x.last and then 4.x.last? >>> >> >>> >> Are there any big changes to basic functionality from 2.6 to 4.x? I'm >>> >> making my way through the change logs but a lot of it is related to >>> >> various features I don't use (at least that which I've read thus far). >>> >> >>> >> >>> >> On 2021-10-02 15:06, Derek Atkins wrote: >>> >>>> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >>> >>> >>> >>> At every version you should load your data file and then save it. >>> >>> >>> >>> While there is no requirement to upgrade, and "if it ain't broke, >>> don't >>> >>> fix it" may apply, if you have a system crash and need to rebuild >>> your >>> >>> system, it'll be easier to use recent versions. >>> >>> >>> >>> -derek >>> >>> Sent using my mobile device. Please excuse any typos. >>> >>> On October 2, 2021 5:56:23 PM AC <[email protected]> wrote: >>> >>> >>> >>>> Ok, I've been running along on 2.6.3 on Win 10.? No issues to date >>> that >>> >>>> I can see. >>> >>>> >>> >>>> I know there's been various changes throughout the rest of the 2.x >>> and >>> >>>> 3.x series and we're now on 4.x which sparks some questions: >>> >>>> >>> >>>> >>> >>>> Do I really need to update?? I only use the basis ledgers for >>> standard >>> >>>> banking accounts, credit cards, loans, mutual funds; scheduled >>> >>>> transactions; and basic reports (typically just the standard >>> transaction >>> >>>> report when I need a list for taxes). I don't use online >>> transactions, >>> >>>> imports, or business features.? Can I assume that the basics still >>> work >>> >>>> the same way? >>> >>>> >>> >>>> If it's better for me to go ahead and update how painful will it be >>> to >>> >>>> update? >>> >>>> >>> >>>> I recall some suggestions previously about upgrading in increments >>> and >>> >>>> if that's the case how many increments am I going to need >>> (hopefully not >>> >>>> one for every point version)? >>> >>>> >>> >>>> _______________________________________________ >>> >>>> gnucash-user mailing list >>> >>>> [email protected] >>> >>>> 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 >>> >> [email protected] >>> >> 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. >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 4 >>> > Date: Sat, 02 Oct 2021 18:20:09 -0400 >>> > From: Derek Atkins <[email protected]> >>> > To: AC <[email protected]>, GnuCash users group >>> > <[email protected]> >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: >>> > <[email protected]> >>> > Content-Type: text/plain; format=flowed; charset="us-ascii" >>> > >>> > Basic features are all the same. >>> > Some options and reports changed along the way, so you might need to >>> > manually File - > Open your data file when you upgrade. And you may >>> lose >>> > saved reports. >>> > >>> > -derek >>> > Sent using my mobile device. Please excuse any typos. >>> > On October 2, 2021 6:13:31 PM AC <[email protected]> wrote: >>> > >>> >> I agree don't upgrade if not absolutely necessary but I will likely be >>> >> replacing this computer in a few months so starting from a newer >>> >> installation is much more likely to happen in that case. >>> >> >>> >> So you're saying I should be able to do three stages of 2.6.last, >>> >> 3.x.last and then 4.x.last? >>> >> >>> >> Are there any big changes to basic functionality from 2.6 to 4.x? I'm >>> >> making my way through the change logs but a lot of it is related to >>> >> various features I don't use (at least that which I've read thus far). >>> >> >>> >> >>> >> On 2021-10-02 15:06, Derek Atkins wrote: >>> >>>> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >>> >>> >>> >>> At every version you should load your data file and then save it. >>> >>> >>> >>> While there is no requirement to upgrade, and "if it ain't broke, >>> don't >>> >>> fix it" may apply, if you have a system crash and need to rebuild >>> your >>> >>> system, it'll be easier to use recent versions. >>> >>> >>> >>> -derek >>> >>> Sent using my mobile device. Please excuse any typos. >>> >>> On October 2, 2021 5:56:23 PM AC <[email protected]> wrote: >>> >>> >>> >>>> Ok, I've been running along on 2.6.3 on Win 10. No issues to date >>> that >>> >>>> I can see. >>> >>>> >>> >>>> I know there's been various changes throughout the rest of the 2.x >>> and >>> >>>> 3.x series and we're now on 4.x which sparks some questions: >>> >>>> >>> >>>> >>> >>>> Do I really need to update? I only use the basis ledgers for >>> standard >>> >>>> banking accounts, credit cards, loans, mutual funds; scheduled >>> >>>> transactions; and basic reports (typically just the standard >>> transaction >>> >>>> report when I need a list for taxes). I don't use online >>> transactions, >>> >>>> imports, or business features. Can I assume that the basics still >>> work >>> >>>> the same way? >>> >>>> >>> >>>> If it's better for me to go ahead and update how painful will it be >>> to >>> >>>> update? >>> >>>> >>> >>>> I recall some suggestions previously about upgrading in increments >>> and >>> >>>> if that's the case how many increments am I going to need >>> (hopefully not >>> >>>> one for every point version)? >>> >>>> >>> >>>> _______________________________________________ >>> >>>> gnucash-user mailing list >>> >>>> [email protected] >>> >>>> 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 >>> >> [email protected] >>> >> 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. >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 5 >>> > Date: Sat, 02 Oct 2021 18:26:35 -0400 >>> > From: Derek Atkins <[email protected]> >>> > To: AC <[email protected]>, <[email protected]> >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: >>> > <[email protected]> >>> > Content-Type: text/plain; format=flowed; charset="us-ascii" >>> > >>> > No, as far as I know, windows does not allow you to have multiple >>> versions >>> > installed. >>> > >>> > -derek >>> > Sent using my mobile device. Please excuse any typos. >>> > On October 2, 2021 6:20:13 PM AC <[email protected]> wrote: >>> > >>> >> Actually, related to this: Is there a straightforward way to try a >>> >> version without having to go through a complete installation on >>> Windows >>> >> and without disturbing the existing installation? >>> >> >>> >> If it's possible then I could run 2.6.last and then 3.x stand-alone >>> with >>> >> a test copy of the file before jumping to 4.x and committing to the >>> full >>> >> install. >>> >> >>> >> On 2021-10-02 15:11, AC wrote: >>> >>> I agree don't upgrade if not absolutely necessary but I will likely >>> be >>> >>> replacing this computer in a few months so starting from a newer >>> >>> installation is much more likely to happen in that case. >>> >>> >>> >>> So you're saying I should be able to do three stages of 2.6.last, >>> >>> 3.x.last and then 4.x.last? >>> >>> >>> >>> Are there any big changes to basic functionality from 2.6 to 4.x? >>> I'm >>> >>> making my way through the change logs but a lot of it is related to >>> >>> various features I don't use (at least that which I've read thus >>> far). >>> >>> >>> >>> >>> >>> On 2021-10-02 15:06, Derek Atkins wrote: >>> >>>>> From 2.6.3 you will need to jump to 2.6.last, then 3.x, then 4.x >>> >>>> >>> >>>> At every version you should load your data file and then save it. >>> >>>> >>> >>>> While there is no requirement to upgrade, and "if it ain't broke, >>> don't >>> >>>> fix it" may apply, if you have a system crash and need to rebuild >>> your >>> >>>> system, it'll be easier to use recent versions. >>> >>>> >>> >>>> -derek >>> >>>> Sent using my mobile device. Please excuse any typos. >>> >>>> On October 2, 2021 5:56:23 PM AC <[email protected]> wrote: >>> >>>> >>> >>>>> Ok, I've been running along on 2.6.3 on Win 10. No issues to date >>> that >>> >>>>> I can see. >>> >>>>> >>> >>>>> I know there's been various changes throughout the rest of the 2.x >>> and >>> >>>>> 3.x series and we're now on 4.x which sparks some questions: >>> >>>>> >>> >>>>> >>> >>>>> Do I really need to update? I only use the basis ledgers for >>> standard >>> >>>>> banking accounts, credit cards, loans, mutual funds; scheduled >>> >>>>> transactions; and basic reports (typically just the standard >>> transaction >>> >>>>> report when I need a list for taxes). I don't use online >>> transactions, >>> >>>>> imports, or business features. Can I assume that the basics still >>> work >>> >>>>> the same way? >>> >>>>> >>> >>>>> If it's better for me to go ahead and update how painful will it >>> be to >>> >>>>> update? >>> >>>>> >>> >>>>> I recall some suggestions previously about upgrading in increments >>> and >>> >>>>> if that's the case how many increments am I going to need >>> (hopefully not >>> >>>>> one for every point version)? >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> gnucash-user mailing list >>> >>>>> [email protected] >>> >>>>> 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 >>> >>> [email protected] >>> >>> 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 >>> >> [email protected] >>> >> 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. >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 6 >>> > Date: Sat, 2 Oct 2021 18:30:44 -0400 >>> > From: Michael or Penny Novack <[email protected]> >>> > To: [email protected] >>> > Subject: Re: [GNC] Making the leap to latest >>> > Message-ID: <[email protected]> >>> > Content-Type: text/plain; charset=windows-1252; format=flowed >>> > >>> > On 10/2/2021 6:11 PM, AC wrote: >>> >> I agree don't upgrade if not absolutely necessary but I will likely be >>> >> replacing this computer in a few months so starting from a newer >>> >> installation is much more likely to happen in that case. >>> > a) Yes, you only want to be making one "change" at a time << FAR easier >>> > to "debug" if there are problems. Since you will not easily have your >>> > current gnucash version available for installation o? the new machine, >>> > best to update now, while still on the old machine, to a current >>> version >>> > you will have available for installing on the new machine. >>> > >>> > b) Going to a new computer, you will want to be saving ALL of your data >>> > (not just gnucash data). If the OS is remaining the same, this is >>> > relatively simple. If the OS will be changing (different on the new >>> > machine) this will not be simple unless the two OS's use the same user >>> > data structure. >>> > >>> > c) In case "b" applies, do not immediately begin the "restore form >>> > backup". Get the software on, and in each case, see where it puts the >>> > application user data. You can then see what files to replace/where. >>> > >>> > Michael D Novack >>> > >>> > >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 7 >>> > Date: Sat, 2 Oct 2021 17:37:34 -0500 >>> > From: Robin Chattopadhyay <[email protected]> >>> > To: john <[email protected]> >>> > Cc: Glenn Fowler <[email protected]>, GnuCash users group >>> > <[email protected]> >>> > Subject: Re: [GNC] Scheduled transactions do not appear in the >>> > register until <enter> is pressed >>> > Message-ID: >>> > <cacyexfv0+b+6qyv-oppc08caxa7leyqfvoksbuyvtbmvoc5...@mail.gmail.com> >>> > Content-Type: text/plain; charset="UTF-8" >>> > >>> > I interpreted the question differently. >>> > >>> > If you leave a register open from a prior session, it seems like the >>> > register view doesn't refresh and display newly created transactions >>> until >>> > you perform some sort of other action that triggers a refresh. That's >>> the >>> > experience *I* thought Glenn was describing. >>> > >>> > Robin >>> > >>> > On Sat, Oct 2, 2021 at 4:56 PM john <[email protected]> wrote: >>> > >>> >> >>> >> >>> >>> On Oct 1, 2021, at 2:58 PM, Glenn Fowler <[email protected]> >>> wrote: >>> >>> >>> >>> Hello all, >>> >>> >>> >>> I have numerous scheduled transactions in multiple books and in >>> settings >>> >>> have them "run when the data file is opened". The transactions do >>> run as >>> >>> expected but do not appear in the register until you press <enter>. >>> >>> With them not appearing, I am not looking at an out of date register >>> >> until >>> >>> I enter a transaction or press <enter>. Wouldn't it make sense for >>> them >>> >> to >>> >>> appear without user input so we are looking at up-to-date books >>> instead >>> >> of >>> >>> trying to create a habit for myself to click <enter> on every open? >>> >> >>> >> That's already possible, just set "create automatically" on the >>> Overview >>> >> page of the Scheduled Transactions Editor. >>> >> >>> >> Regards, >>> >> John Ralls >>> >> >>> >> _______________________________________________ >>> >> gnucash-user mailing list >>> >> [email protected] >>> >> 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. >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 8 >>> > Date: Sat, 2 Oct 2021 18:32:15 -0400 >>> > From: Glenn Fowler <[email protected]> >>> > To: john <[email protected]> >>> > Cc: Glenn Fowler <[email protected]>, GnuCash users group >>> > <[email protected]> >>> > Subject: Re: [GNC] Scheduled transactions do not appear in the >>> > register until <enter> is pressed >>> > Message-ID: >>> > < >>> sj0pr19mb444552a7ec1f1dea3764fb8f8f...@sj0pr19mb4445.namprd19.prod.outlook.com >>> > >>> > >>> > Content-Type: text/plain; charset="UTF-8" >>> > >>> > Hi John, >>> > >>> > I already have "create automatically" checked and scheduled >>> transactions do >>> > create automatically as expected. The issue is if GnuCash is opened >>> after >>> > the transaction is created, they do not appear in the register until >>> you >>> > press <enter> which can create issues because you are looking at an >>> > out-of-date register. >>> > >>> > On Sat, Oct 2, 2021 at 5:56 PM john <[email protected]> wrote: >>> > >>> >> >>> >> >>> >>> On Oct 1, 2021, at 2:58 PM, Glenn Fowler <[email protected]> >>> wrote: >>> >>> >>> >>> Hello all, >>> >>> >>> >>> I have numerous scheduled transactions in multiple books and in >>> settings >>> >>> have them "run when the data file is opened". The transactions do >>> run as >>> >>> expected but do not appear in the register until you press <enter>. >>> >>> With them not appearing, I am not looking at an out of date register >>> >> until >>> >>> I enter a transaction or press <enter>. Wouldn't it make sense for >>> them >>> >> to >>> >>> appear without user input so we are looking at up-to-date books >>> instead >>> >> of >>> >>> trying to create a habit for myself to click <enter> on every open? >>> >> >>> >> That's already possible, just set "create automatically" on the >>> Overview >>> >> page of the Scheduled Transactions Editor. >>> >> >>> >> Regards, >>> >> John Ralls >>> > >>> > >>> > ------------------------------ >>> > >>> > Message: 9 >>> > Date: Sat, 2 Oct 2021 19:19:42 -0500 >>> > From: Robin Chattopadhyay <[email protected]> >>> > To: Gnucash Users <[email protected]> >>> > Subject: Re: [GNC] OFX Import with Investment Transactions >>> > Message-ID: >>> > <cacyexftwao8tedz-w8kh9c3l-yv7mjp4uh19x8vgizj70nv...@mail.gmail.com> >>> > Content-Type: text/plain; charset="utf-8" >>> > >>> > Hi Jean- >>> > >>> > I understand the logic for #1 and have no concerns about that. >>> > >>> > As for #2, I did continue past the first matching dialog and there >>> were no >>> > additional dialogs, the focus returned to the account list. >>> > >>> > There are definitely FITIDs that are already in the database that are >>> also >>> > in the most recent OFX file. This is because the provider doesn't >>> allow you >>> > to specify a date range, only 'current quarter' or 'some other >>> quarter'. >>> > >>> > I tried something else to research... >>> > >>> > Using 4.8, I created a blank file and then imported an OFX file from >>> Sep. >>> > 25, 2021. This file had 66 transactions and imported as expected with >>> one >>> > matcher screen per security/account as you indicated would happen. I >>> then >>> > attempted to import the OFX file from Oct. 2. This file has 84 >>> transactions >>> > -- the same 66 transactions from the Sep. 25 file plus 18 new >>> transactions >>> > dated 9/24. >>> > >>> > The program then presents the dialog for the first account. There are >>> two >>> > transactions in the most recent file for this account; however they're >>> > already in the database, thus triggering the message "OFX file >>> > /home/robin/Downloads.qfx' imported transactions for account 'xxx' 2 >>> > transactions processed, no transactions to match". That makes sense as >>> > those are older transactions that are already in the database. I >>> clicked >>> > 'Close' for that dialog and then the focus returns to the main >>> application. >>> > It's almost as if the program -- having determined that there were no >>> new >>> > transactions to import into the first account -- decided not to look >>> at the >>> > subsequent accounts. >>> > >>> > In service to the greater good, I am attaching the test file I created >>> and >>> > the Oct. 2 OFX file. I have removed all of the position data (there are >>> > limits to what I'm willing to share :-) ), but that will not negatively >>> > affect the import process. >>> > >>> > Something else that I just noticed... >>> > >>> > If -- after importing the OFX file -- you open one of the account >>> > registers, you'll see duplicate transactions! Although, if you close >>> and >>> > re-open the file, those duplicated transactions do not appear when you >>> > re-open the account register. I don't know what to make of that. >>> > >>> > On Sat, Oct 2, 2021 at 1:52 PM Jean L <[email protected]> wrote: >>> >> >>> >> Yes, there's a new behavior with OFX import. The match dialog shows up >>> >> for each target account, so if you're importing securities the dialog >>> >> will show up for each security. This could be a real annoyance if >>> there >>> >> are many different securities, so we may want to change that behavior. >>> >> The new behavior was introduced to fix an issue when a single OFX file >>> >> had transfers between accounts. >>> >> >>> >> I see two issues here: >>> >> 1) The fact that the match dialog runs for each target account (see >>> >> comment above) >>> >> 2) The fact that some of your imported transactions were simply >>> ignored. >>> >> >>> >> About 2): Did you try to continue with the import after the first >>> >> matching dialog? Did it then go to the next securities? Or did you >>> just >>> >> abort thinking something was wrong (not expecting the new behavior of >>> >> seeing the matching dialog for each security instead of all together >>> as >>> >> before) >>> >> >>> >> If that was not the case (i.e., you tried continuing but nothing else >>> >> happened) one reason why this could happen is if the FITID used for >>> the >>> >> imported transactions were already present in the target account. This >>> >> is new in the latest version: transactions that were previously >>> imported >>> >> are no longer shown the matching dialog. In your case this seems >>> >> erroneous. So either it's a bug (i.e., the FITID of the imported >>> >> transactions are NOT found in any of the transactions of the account >>> >> you're imported into, so they should show) or it's a problem with the >>> >> OFX data that the transactions seem to reuse existing FITIDs. >>> >> The fact that things work normally when you import into a blank >>> account >>> >> would indicate that indeed, the FITID of the imported transactions >>> >> already exist in your target account. >>> >> >>> >> SO, could you re-try importing with the latest version, but making >>> sure >>> >> you continue clicking OK for each match dialog? Does this work or not? >>> >> If not, then we'll need to check whether the FITID of the new imported >>> >> transactions somehow have been used before in the previously imported >>> >> transactions. To see that, you'd need to pick one that was not >>> imported >>> >> (looking at the OFX file), get its FITID, and see in your account >>> >> database (save it as an xml file so it can be looked at with a regular >>> >> editor) whether that FITID exists. >>> >> >>> >> Jean >>> >> >>> >> On 10/2/2021 8:58 AM, Robin Chattopadhyay wrote: >>> >>> Ubuntu 20.04 LTS (VMWare virtual machine in case that matters) >>> >>> Gnucash 4.8 >>> >>> libofx 0.9.15 >>> >>> >>> >>> I tried importing an OFX file from my 401K provider this morning and >>> I >>> > got >>> >>> a message box that said it had imported 2 transactions for a single >>> >>> security in the file and there were no additional transactions to >>> > process. >>> >>> This was incorrect as there were 18 new transactions across nine >>> > securities >>> >>> (along with a number of other transactions that had already been >>> > imported >>> >>> previously). >>> >>> >>> >>> I tried a number of things to resolve (after taking a backup, of >>> > course): >>> >>> 1 - Tools > Import Map Editor and deleted all of the associations for >>> > this >>> >>> file. When I re-imported, I was prompted to map each security in the >>> > file >>> >>> to the correct account. No issues there. But when importing the OFX >>> file >>> >>> again, I had the same experience as described above >>> >>> 2 - Created a blank file and attempted to import the file there. >>> Through >>> >>> the import process, I created new securities and new accounts, >>> nothing >>> >>> unexpected there. Then the generic transaction importer dialog popped >>> > up, >>> >>> but with just the two transactions for the same security cited in the >>> >>> original problem dialog. I imported those, clicked OK and then the >>> > generic >>> >>> transaction importer dialog came up *again* but only with >>> transactions >>> > for >>> >>> a single, different security. I imported those and repeated the >>> process >>> > for >>> >>> each security with transactions in the file. Each time the generic >>> >>> transaction importer dialog came up, it only had transactions for a >>> > single >>> >>> security. This is definitely new behavior that I didn't see in 4.6. >>> >>> Previously the import dialog had all the new transactions in the file >>> >>> 3 - Reverted to 4.7. Crashed when selecting Import from the File menu >>> >>> (Trace/breakpoint trap (core dumped). Not unexpected, but thought I >>> > would >>> >>> try anyway. >>> >>> 4 - Reverted to 4.6. This works as it used to with all the new >>> > transactions >>> >>> in a single dialog >>> >>> >>> >>> Finally, I don't know if this matters, but I scanned stdout from the >>> >>> build/make/install process to see if anything looked obviously wrong >>> > and I >>> >>> found this (I don't know if it's relevant): >>> >>> >>> >>> -- Performing Test HAVE_OFX_BUG_39 >>> >>> -- Performing Test HAVE_OFX_BUG_39 - Failed >>> >>> >>> >>> Thanks, >>> >>> Robin >>> >>> _______________________________________________ >>> >>> gnucash-user mailing list >>> >>> [email protected] >>> >>> 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 >>> >> [email protected] >>> >> 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. >>> > -------------- next part -------------- >>> > A non-text attachment was scrubbed... >>> > Name: robin.qfx >>> > Type: application/octet-stream >>> > Size: 56427 bytes >>> > Desc: not available >>> > URL: >>> > < >>> http://lists.gnucash.org/pipermail/gnucash-user/attachments/20211002/4d9fdfdc/attachment.obj >>> > >>> > -------------- next part -------------- >>> > A non-text attachment was scrubbed... >>> > Name: test-file.gnucash >>> > Type: application/x-gnucash >>> > Size: 10338 bytes >>> > Desc: not available >>> > URL: >>> > < >>> http://lists.gnucash.org/pipermail/gnucash-user/attachments/20211002/4d9fdfdc/attachment.bin >>> > >>> > >>> > ------------------------------ >>> > >>> > Subject: Digest Footer >>> > >>> > _______________________________________________ >>> > >>> > gnucash-user mailing list >>> > [email protected] >>> > 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. >>> > >>> > >>> > ------------------------------ >>> > >>> > End of gnucash-user Digest, Vol 223, Issue 6 >>> > ******************************************** >>> >>> _______________________________________________ >>> gnucash-user mailing list >>> [email protected] >>> 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 [email protected] 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.
