Tags from 5.1.3 do not appear in any ledger views in 5.2.2. Exception: they appear if the transaction was a transfer.
Tags on the sidebar menu still show my tags and transactions from 5.1.3.
I can run a report on a tag from 5.1.3 and it will include all transactions with that tag. However, if you add a tag column, even though the report pulled the transactions correctly from 5.1.3, the tag column shows “No Tag”.
If I enter a new transaction and add a tag, the tag will appear in the ledger views correctly.
If I enter a tag on an old transaction that already has the same tag: it appears correctly in the ledger view but in the tag view there is a shift in the columns with the category appearing in the account column, the account appears in the detail column and the amount moves from decrease to increase.
Based on this I cannot transition my data file from 5.1.3 to 5.2.2 without introducing errors if I change an old transaction for any reason.
Will there be any resolution to this issue? Unfortunately, I use tags on every transaction.
This has not been forgotten, but I don’t believe any good solution has yet presented itself. The issue has to do with which split a tag was applied to in 5.1.3. If you invoke the Transaction/Show Transaction Details function, you will see where the tag it applied. I suspect if you add the tag to the other split, at least some of your problems will resolve. You may need to go to the ledger of the other account (Category) to do this. Your data is not lost, and I’m pretty sure you are not introducing any errors by editing in a newer KMM a transaction created in an older version.
Is there any way to mass update in the data file in either 5.1.3 or 5.2.2 to add the tags to both sides of the transaction. In other words, can I mass update the tags added in 5.1.3 to the other side of the transaction in 5.2.2. (I use tags on every transaction, so updating transaction by transaction, especially in a data file going back to 2010 would be impossible.)
Not at all impossible, but certainly not realistic. You could file a wishlist bug to request such a feature, but I’m not sure it would get a high enough priority to get implemented.
Unfortunately, the only current way I can think of to do this would be to edit the data file itself. If you use a .kmy file, that is just a gzipped .xml file, which is plain text. The file might be encrypted with gpg. Personally, I am a Perl bigot and would use that. Python would do. I’m not familiar enough with sed and awk, but I suspect those could also work. An example transaction with a tag in one split is:
<TRANSACTION id="T000000000000001936" postdate="2010-02-03" memo="" entrydate="2010-02-08" commodity="USD">
<SPLITS>
<SPLIT id="S0001" payee="P000396" reconciledate="2010-04-29" action="" reconcileflag="2" value="-6/1" shares="-6/1" price="1/1" memo="TACF trip, airport snack, Tri-Cities" account="A000103" num
ber="" bankid="">
<TAG id="G000003"/>
</SPLIT>
<SPLIT id="S0002" payee="" reconciledate="" action="" reconcileflag="0" value="6/1" shares="6/1" price="1/1" memo="TACF trip, airport snack, Tri-Cities" account="A000184" number="" bankid=""/>
</SPLITS>
</TRANSACTION>
What you need to do is take the and copy it (leave the original) to the other split. I don’t think there is any guarantee that the tag will always be on the first split, but I am not certain. Note also, this would not apply to transactions with only one split (which are not common,) and might apply to transactions with more than two splits (so called split transactions.) If all tags in your data file are in the first split, then any of the above mentioned tools should work, but if not, a programming/scripting language would be necessary.
Thanks for the info!
This is probably beyond me now without a long learning curve. My programming skills date back to the PBx…
I will probably wait for a multi-selector for the tag field before I move to 5.2.x.
The multi-selector is working on 5.2.2 but still need a way to update the tags, especially when multiple tags are selected in one transaction.
Sorry, but I seem to have made some wrong assumptions. It IS possible to edit multiple transactions at once, and add a tag (it does not add a second copy if a tag is already assigned to a split.) I don’t remember if you have brought this up in any other forum, but the issue is that tags are now attached to each split, not directly to the transaction, and many old tags only got added to one of the two splits. The ledger is showing the data from the split for the account being shown. Most standard transactions have two splits: one for the account and one for the category (which are just income or expense accounts.)
However, batch editing is not possible directly in the Tags View. So, you need to select a bunch of transaction either in the account or category view, Transaction/Edit, and add the required tag. I’ve only tested briefly, so do some testing and keep plenty of backups. I suspect the difficulty will be selecting enough transactions for each edit that it is sufficiently better than just doing one at a time.
The new split tagging system in 5.2 is very confusing, and completely broke my workflow. Now if I want to properly tag my transactions created from Ledgers → Account view, I have to switch to the Ledgers → Category view. Why can’t I create an account split tag from the account? It used to work just fine.
From my observation tagging from the Ledgers → Account view tags the category split, and tagging from the Ledgers → Category view tags the account split. This seems completely backward. Tagging from the Payee view also tags the category split as well. The most confusing part is there’s no visibility into which split is being tagged, and you cannot see the tags on the other split at all.
I have been using tags for tracking what is effectively a sub-category all transactions, as well as for tracking transaction types. I just cleaned up my tags and removed all the tags for the sub-category and just retained transaction type.
There is only one transaction type per transaction so I can use the multi-selector for tags in each account to select the tags I want to update. I select all the transactions of a type/tag, eg Paypal, then select edit and type in Paypal and hit save. Paypal is then added to both sides of the transaction!
So as long as you have only one tag per transaction you can use the multi-selector and edit to add the single tag from 5.1.3 to both sides of the transaction in 5.2.2. But you do have to do it in the ledger, account by account.
Now I just need to wait for the next update to see if it addresses some of the other issues which I have (esp display) before upgrading. But at least I can mark the tag issue solved.
Just to clarify, editing the tag in this way does add it to the second side of the transaction!