[Kmymoney-devel] imported transactions not being matched

[Chris]

Hi Jack

I suspect you are correct. I was hoping someone would recall the reasoning 
so we could work on a fix with all the necessary info.

If the reason has been lost in the mists of time. Then I'll clean up my code 
changes (which were very rough just to do the testing) and put it in for review.

Chris
Rebel Software <http://www.rebel.com.au>

On 26/04/2014 9:55 AM, Jack wrote:
> I vaguely recall that this has come up before, with about the same (lack 
> of) remembered reason for the restriction.  However, given that you found 
> multiple explicit checks, whoever developed that bit of code must have had 
> a reason, although perhaps we are lucky enough that it simply doesn't 
> apply any more.  I suggest filing an enhancement request at bugs.kde.org 
> (if there isn't already one - I haven't checked) just to put it officially 
> on record.  If you have already looked into the code, then a reviewboard 
> request might not be out of order.
>
> To be long winded, I suspect what may have changed since that code was 
> written was the general use case.  At that point, the most common scenario 
> (yes, I'm just guessing, but ....) was KMM mostly used manually, with 
> someone just starting to download and import statements from either a bank 
> or credit card.  Now, with ofx-direct connect (and I suppose aqbanking and 
> other methods I am not familiar with) we have accounts where the primary 
> input is importing, and transactions between accounts each of which has 
> its own primary import are now much more common.
>
> Jack
>
> On 2014.04.25 20:11, Chris wrote:
>> No Takers?
>>
>> I have commented out the checks that prevent the matching of imported 
>> transactions. KMM then correctly manually matched the transactions. I 
>> haven't had the opportunity to test matching during import.
>>
>> So the remaining questions is why was matching disabled on two imported 
>> or two manually entered transactions. There was checks to prevent it in 
>> at least 3 different locations.
>>
>> Is there a subtle bug that creeps in if these checks are removed?
>>
>> If there is no (remembered) reason to prevent the matching of imported 
>> files then I suggest this "feature" be removed. Though this feature is 
>> documented there is no documentation I could find that gives a hint as to 
>> why.
>>
>> Chris
>>
>> On 25/04/2014 10:13 AM, Chris wrote:
>>> Hey all
>>>
>>> I am having an issue with imported transactions not being automatically 
>>> matched and manual matching is disabled.
>>>
>>> both transactions are the result of seperate imports one from my credit 
>>> card statement the other from a bank statement
>>>
>>> both transactions are for a payment from my bank account to the credit card
>>> Both are on the same date with the same amount the only differences are 
>>> the memo and payee fields
>>>
>>> They should have automatically matched. but didn't and I assume because 
>>> they are both imported I cannot manually match them.
>>>
>>> Questions
>>>
>>> 1/ How can I correct this?
>>> 2/ What is the thinking behind disabling the matching when both are 
>>> imported or manually entered?
>>>
>>> documentation is here..
>>> http://docs.kde.org/stable/nl/extragear-office/kmymoney/details.ledgers.match.html 
>>>
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> KMyMoney-devel mailing list
>> KMyMoney-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kmymoney-devel
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20140426/e1c8a9ac/attachment.html>