On the transaction entry form under Transaction Type there is an option Duplicate. What does it mean? I have tried it and it does not enter the transaction twice so what is it and how do I make use of it?
Thanks
What is the 'Duplicate' status in the Transaction Type field
Moderator: Renato
-
- New User
- Posts: 2
- Joined: Thu Aug 27, 2015 4:02 pm
- Are you a spam bot?: No
-
- Developer
- Posts: 1535
- Joined: Sat Dec 06, 2008 2:27 pm
- Are you a spam bot?: No
- Location: Sankt-Petersburg, Russia
Re: What is the 'Duplicate' status in the Transaction Type f
IMHO it has been designed for mark some transactions if it the same as already present one (after import, for example). Then you can view all 'duplicate' transactions and delete them.
Re: What is the 'Duplicate' status in the Transaction Type f
I wish it did what you thought it did, which is what i thought it did originally too.
-
- Senior User
- Posts: 42
- Joined: Fri Oct 29, 2010 9:48 pm
- Are you a spam bot?: No
- Location: London, England
Re: What is the 'Duplicate' status in the Transaction Type f
Oh the joy of the English language, where a single word can be both a verb and a noun and only context gives clear meaning as to its use. In this case, of course, it's the noun - you are not duplicating an entry but showing that the entry is a duplicate of another. I have to say that, in all the time I've been using MMEX, I've not yet found a pressing need to duplicate an entry but I have found several duplicates that were errors so, for me, the way it's used in this programme suits me. Perhaps I am just one of the lucky onessterling wrote:I wish it did what you thought it did, which is what i thought it did originally too.
Paul, MMEX user since April 2010
Re: What is the 'Duplicate' status in the Transaction Type f
Very true. Two pronunciations of the same word duplicate. I often duplicate transactions though, such as transfering money between my accounts each month.paulcroft wrote:Oh the joy of the English language, where a single word can be both a verb and a noun and only context gives clear meaning as to its use. In this case, of course, it's the noun - you are not duplicating an entry but showing that the entry is a duplicate of another. I have to say that, in all the time I've been using MMEX, I've not yet found a pressing need to duplicate an entry but I have found several duplicates that were errors so, for me, the way it's used in this programme suits me. Perhaps I am just one of the lucky onessterling wrote:I wish it did what you thought it did, which is what i thought it did originally too.
-
- New User
- Posts: 6
- Joined: Sat Oct 24, 2015 10:49 am
- Are you a spam bot?: No
- Location: UK
Re: What is the 'Duplicate' status in the Transaction Type f
In MMEX Help under 'Creating New Transactions' and on the MMEX website under Features > Transactions it says "Duplicate: The status will be automatically be changed to duplicate if it is recognized as such." As I understand it, this is just a flag so you can review the transaction and check if it is a duplicate or not, and either delete or void the transaction if it is, or change the status if it isn't.
I guess this is particularly useful when importing your transactions by CSV, and MMEX will hopefully automatically flag any duplicates. For example, you might have already entered a transaction manually or via Recurring Transactions, and the same transaction is then imported from your CSV bank statement, which will need to be flagged for deletion. Or where you are importing CSV transactions from two different banks (e.g. bank account and credit card account), a transfer from one account to the other will appear on both statements, but it will only need to appear as one transfer transaction in MMEX, so the duplicate should be deleted.
I guess this is particularly useful when importing your transactions by CSV, and MMEX will hopefully automatically flag any duplicates. For example, you might have already entered a transaction manually or via Recurring Transactions, and the same transaction is then imported from your CSV bank statement, which will need to be flagged for deletion. Or where you are importing CSV transactions from two different banks (e.g. bank account and credit card account), a transfer from one account to the other will appear on both statements, but it will only need to appear as one transfer transaction in MMEX, so the duplicate should be deleted.