Re: [GNC] ANNOUNCE: GnuCash 4.10 Released
Wanted to give a quick CONGRATS on this new release with added features.
Great work adding the new features on generic import transaction matcher
of ofx/qfx specifically append on updating and clearing and ability to
edit description/memo/notes. I had been missing the ability to put what
the purchase was for on an entry during import and having to go back
after import to update the details.
On 3/27/2022 7:40 PM, Ken Pyzik wrote:
Version 4.10 downloaded and tested on Windows 11 - no issues. Everything works
great from the limited testing I did. Thank you for your hard work!
-Original Message-
From: gnucash-user On
Behalf Of John Ralls
Sent: Sunday, March 27, 2022 4:20 PM
To: gnucash-annou...@lists.gnucash.org
Cc: GnuCash users group ; GnuCash Developers
Subject: [GNC] ANNOUNCE: GnuCash 4.10 Released
The GnuCash development team announces GnuCash 4.10, the eleventh release in
the stable 4.x series
Between 4.9 and 4.10, the following bugfixes were accomplished:
Bug 684507 - commodity namespace should be localized
Bug 741674 - Newly created Scheduled Transactions appear in existing
search windows
Bug 797501 - Currency symbols in Hebrew (RTL) language
Bug 797772 - Allow reconciliation report to double filter by both posting
and reconciliation date
Bug 798164 - Import transaction window does not allow changing the
transaction description.
Bug 798272 - up/down arrow keys do not work in account selection pop-up
Bug 798375 - Transfer Account Selection not editable after typing error
Bug 798386 - Cannot increment date by 1 day with Japanese keyboard.Allow
';' to increment the date because on those keyboards + is shift-;.
Bug 798391 -OFX import routine keeps prompting for accepted (and
reconciled) transactions when imported again
Bug 797610 - Scrolling is too fast to follow
Bug 798392 - Reports do not display when Reports JavaScript dependencies are located
at a filepath that includes special characters like hash ("#")
Bug 798395 - ofxdirectconnect downloads crash gnucash 4.9
Bug 798408 - The calculation in budgets UI and reports are wrong.
Bug 798411 - Untranslated/Unused string [pt only]
Bug 798415 - Due Bills Reminder Dialog - Right align 'amount'This was a
right-to-left language (e.g. Hebrew) problem.
Bug 798435 - Crash on print after printing checks
Bug 798438 - on reconcile window, click on the last column 'R' does not
order the entries according with the status
Bug 798448 - Column 'num' cannot be null
Bug 798458 - Build failure with gcc 12
Bug 798474 - Windows 10: Mouse scroll wheel on register only scrolls 1
pixel at a time (instead of 1 line at a time)
The following fixes and improvements were not associated with bug reports:
Added a BETA Stock Transaction Assistant to help create a variety of
securities transactions. To try it out start GnuCash with the --extra option, open
a stock-type register, and select Actions>Stock Assistant. Please note any
issues on Bug 798004.
Remove the hard-coded default namespaces"AMEX", "NASDAQ", "NYSE", "EUREX", and
"FUND" from the New Security dialog. These namespaces were added to the list of existing namespaces; it was necessary
to create a commodity that used one of them to make that one an actual namespace, so users who have commodities in e.g. the
namespace NYSE will still see that namespace in the selection list. Reasoning: The list was necessarily incomplete and confused
new users.
Fixed the Income Statement report table formating so that all sections get
laid out to the same width.
[Python Bindings]Implement some comparison and arithmetic operators for
GncNumeric
Budgets are sensitive to readonly status
Disable some budget features if book is readonly
Fix suppression of "cut split/transaction" warnings for the current session
These were not working because they were missing from the temporary
warnings settings schema. The warnings could only be dismissed permanently. Add
them to the temporary warnings section of the settings schema.
Currencies in several locations not displayed correctly for Hebrew
[category-barchart] Added option to show ratios
[html-chart] Add format style option for numbers
Better wording for tax table changed info message.
[register] Checkbox any value other than 0x20 (ASCII space) is true,
because it can be X or U+2716 now and could be something else in future. Fixes
in particular the disappearing tax-included and tax-table in the Invoice/Bill
entry register.
[Python Bindings]Provide the complete set of QOF enums in gnucash
[Pyton Bindings]Provide wrapper for qof numeric predicate
Python bindings already have some wrapping objects for qof predicates.
This adds the one missing for GncNumeric comparisons. Additionally fixes a
wrong number for QOF_NUMERIC_MATCH_ANY in example file.
Remove commodity-table.scm,
Re: [GNC] How to Manually Match transactions
Have some good news and an even better solution that can be added to the FAQ or How-to. 2 Options that work for associating/matching a transaction that does not import match: 1 - Import from Account A and assign to Account B at import or before importing Account B. Then when importing Account B, the two transactions will be matched to each other. This is the proactive correct solution. So obvious. 2 - In the case import QFX from Account A and match is not made before hand, then importing Account B won't find a match. Fix is to assign either Account A or Account B transaction to the other account respectively. Then delete the duplicate transaction, lets say, account B has two entries because Account A was assigned to Account B as the destination. Now, re-import Account B and the import matcher will now match those two entries, success. Again, option 1 is what you want and option 2 is a good recovery to fix the issue. On 11/19/2020 9:58 PM, Griff wrote: Thanks for the great suggestions everyone. I tried the idea of changing from A to C during import and then looking for a match but no matches were present to select from in the matcher dialog. I even manually changed the date of the transaction in account A to match the date of account B before importing, then did the import and the matcher still did not find anything to offer up. Too bad GnuCash does not allow selecting the match from the full list of transactions or matching at other times besides import. Hopefully this was a special case match issue and the norm will be to find a match for the transfers like your example of PayPal and the multi-day float. Otherwise, I can manually fix the issue or use Frank's short-term float account "money in transfer" to match the transactions. I have the default import setting of bayesian and 1, 3, 6 for thresholds, I tried changing the match display threshold to 0 but no impact. As a side note, I tested the QIF file for the same transactions instead to see if that worked better and had the strange issue of GnuCash hanging. Tried it several times with the same issue. David places like PayPal/Venmo still enjoy the float on their end and offer a rapid no-float option for a fee, win-win for them. On Thu, Nov 19, 2020 at 5:54 PM David Carlson <[1]david.carlson@gmail.com> wrote: In the olden days some people would even try to take advantage of having a lot of funds in "float" between various bank accounts. 來 On Thu, Nov 19, 2020, 6:12 PM Adrien Monteleone < [2]adrien.montele...@lusfiber.net> wrote: > Griff, > > Sorry, I misunderstood the original post. I thought it was a single > import, not two separate ones. > > David's suggestions should be the way to go in your case. > > As for retaining the second date, (presumably from the Credit Card > account) see my reply to Frank. > > Regards, > Adrien > > On 11/19/20 3:18 PM, Griff wrote: > > Thanks Adrien and Stephen. > > > > Both your solutions are good work arounds, sounds like the short answer > is > > it can't be done the nice way preserving data. The result will be to > > manually delete one of the import transactions and the new duplicate > > created won't have the date that matches one of the 2 banks for > correctness > > purposes. > > > > To your suggestion of importing it all at once, that is not possible as > one > > QFX file is from the credit card company download and the other QFX is > from > > the different bank company's download. They will be two files. > > > > This is unfortunate as the matcher is only run on QIF import and not > > OFX/QFX import. > > Should I be getting the data from the banks in QIF instead, does that > work > > better then OFX/QFX for GnuCash import? > > > ___ > gnucash-user mailing list > [3]gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > [4]https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > [5]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 [6]gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: [7]https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see [8]https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember
