me I saved, the
> > consistency check came up with over 4000 problems. ALL are in
> > investment accounts, several of which have been closed for many
> > years. I suspect it's an unintended side effect of the recent
work on
> > storing prices for add/remove share transact
On Mittwoch, 22. Januar 2025 07:11:54 CET Ralf Habacker via KMyMoney-devel
wrote:
> Hi Jack,
>
> Am 22.01.25 um 02:12 schrieb Jack via KMyMoney-devel:
> > I just compiled a fresh version, and the first time I saved, the
> > consistency check came up with over 4000
Hi Jack,
Am 22.01.25 um 02:12 schrieb Jack via KMyMoney-devel:
I just compiled a fresh version, and the first time I saved, the
consistency check came up with over 4000 problems. ALL are in
investment accounts, several of which have been closed for many
years. I suspect it's an unint
I just compiled a fresh version, and the first time I saved, the
consistency check came up with over 4000 problems. ALL are in
investment accounts, several of which have been closed for many years.
I suspect it's an unintended side effect of the recent work on storing
prices fo
https://bugs.kde.org/show_bug.cgi?id=495438
--- Comment #3 from Jack ---
Thanks for letting us know. Also, when replying to a bug by email, PLEASE
remove everything from your message except your response, as your entire
message becomes the next comment to the bug, and the extra, duplicated, quot
ummary|Consustency check |Consistency check
> Status|REPORTED|RESOLVED
> Resolution|--- |NOT A BUG
>
> --- Comment #1 from Jack ---
> I see no bug here, but a question about using the program. This is best
> h
https://bugs.kde.org/show_bug.cgi?id=495438
Jack changed:
What|Removed |Added
Summary|Consustency check |Consistency check
Status|REPORTED
hen reconciling my
> holdings in that investment account, that stock was not shown on the
> Investments View, Equities tab.
>
> Should the consistency check look for any closed accounts which are not
> empty? I'm not sure if it should automatically reopen them, or just
, Equities tab.
Should the consistency check look for any closed accounts which are not
empty? I'm not sure if it should automatically reopen them, or just
let the user decide what to do - although if you want to move the
content (money or stock) you have to reopen the account first.
Thoughts?
Jack
https://bugs.kde.org/show_bug.cgi?id=463526
Bug ID: 463526
Summary: Improve consistency check report so that parts can be
copied to the clipboard
Classification: Applications
Product: kmymoney
Version: git (master
https://bugs.kde.org/show_bug.cgi?id=429909
Bug ID: 429909
Summary: Consistency check failed after changing to opening
date
Product: kmymoney
Version: 5.1.0
Platform: Microsoft Windows
OS: Microsoft Windows
https://bugs.kde.org/show_bug.cgi?id=428324
Suresh PB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
|--- |WAITINGFORINFO
--- Comment #6 from Thomas Baumgart ---
In the original report, the error message "Consistency check found the category
as other type, so creating new category under income." is referenced. I cannot
find such a message in the source code. Please provide th
https://bugs.kde.org/show_bug.cgi?id=428324
--- Comment #5 from Jack ---
You can save your kmy file as anon.kmy
[https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.formats.anonymous.html]
and you can alter any personal data in the csv file. If someone else cannot
replicate your pr
https://bugs.kde.org/show_bug.cgi?id=428324
--- Comment #4 from Suresh PB ---
I don't have a dummy data.
Thank you,
PB Suresh
On Wed, Oct 28, 2020, 7:38 PM Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=428324
>
> --- Comment #3 from Jack ---
> Can you provide a kmy file and csv file tha
https://bugs.kde.org/show_bug.cgi?id=428324
--- Comment #3 from Jack ---
Can you provide a kmy file and csv file that exhibit the problem?
--
You are receiving this mail because:
You are the assignee for the bug.
manually add two
> deposit transactions, one with an expense category and one with an income
> category. Saving did not trigger any message from the consistency check, so
> it might well have something to do with the transactions being imported.
Manual entries does not trigger consistency check
, manually add two deposit
transactions, one with an expense category and one with an income category.
Saving did not trigger any message from the consistency check, so it might well
have something to do with the transactions being imported. What type was the
import? OFX, csv, qif?
--
You are
https://bugs.kde.org/show_bug.cgi?id=428324
Bug ID: 428324
Summary: Consistency check post import has issue
Product: kmymoney
Version: 5.0.6
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=365133
Ralf Habacker changed:
What|Removed |Added
CC||ralf.habac...@freenet.de
Version Fixed In|4.8
https://bugs.kde.org/show_bug.cgi?id=325441
Andrew Crouthamel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=325441
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #7 from Andrew Croutham
https://bugs.kde.org/show_bug.cgi?id=325441
Jack changed:
What|Removed |Added
CC|ostroffjh@users.sourceforge |
|.net|
--- C
https://bugs.kde.org/show_bug.cgi?id=325441
Ralf Habacker changed:
What|Removed |Added
Version|unspecified |4.6.1
CC|
https://bugs.kde.org/show_bug.cgi?id=350903
Ralf Habacker changed:
What|Removed |Added
Version Fixed In|4.8 |4.8.0
CC|
https://bugs.kde.org/show_bug.cgi?id=253493
Michael Carpino changed:
What|Removed |Added
CC||mfcarp...@gmail.com
Status|REOPEN
https://bugs.kde.org/show_bug.cgi?id=350903
NSLW changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In||4.
https://bugs.kde.org/show_bug.cgi?id=365133
Thomas Baumgart changed:
What|Removed |Added
Version Fixed In||4.8.1
--
You are receiving this mail because
00:19.
Pushed by aacid into branch 'master'.
Exclude IncomeExpense categories from opening date price consistency check
REVIEW: 129702
M +4-1kmymoney/mymoney/mymoneyfile.cpp
https://commits.kde.org/kmymoney/365c0f4fa75a291ff7447123cd0ca7b10c41f2bd
--
You are receiving
5ee94f58c7b43e5640bacce754c1e7a6720c7c5f by Albert Astals Cid, on
behalf of Mark Jones.
Committed on 21/01/2017 at 00:16.
Pushed by aacid into branch '4.8'.
Exclude IncomeExpense categories from opening date price consistency check
REVIEW: 129702
M +4-1kmymoney/mymoney/mymon
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129702/
---
(Updated Jan. 21, 2017, 12:17 a.m.)
Status
--
This change has been m
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129702/#review101570
---
Ship it!
Ship It!
- Thomas Baumgart
On Dez. 24, 2016,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129702/
---
Review request for KMymoney.
Bugs: 365133
http://bugs.kde.org/show_bu
https://bugs.kde.org/show_bug.cgi?id=365133
--- Comment #2 from Thomas Baumgart ---
I currently don't see a problem with the proposed fix and don't expect any
side-effects either. So please go ahead and submit your review request.
--
You are receiving this mail because:
You are the assignee for
have a fix for this bug but I am concerned about potential side-effects. My
fix is to exclude accounts of type IncomeExpense from the consistency check for
missing prices on the opening date (mymoneyfile.cpp:2337).
Is there any reason that a IncomeExpense category in a foreign (non-base)
currency
On 2016.11.18 11:02, Steven Third wrote:
Hello.
I'm using version 4.8.0 of your excellent program and have been for
some time now. On previous versions the consistency check was a user
option it now appears when I save file. The warnings are irrelevant
and have no bearing on the acc
Hello.
I'm using version 4.8.0 of your excellent program and have been for some
time now. On previous versions the consistency check was a user option
it now appears when I save file. The warnings are irrelevant and have no
bearing on the accuracy of my accounts. I wonder if there is an
https://bugs.kde.org/show_bug.cgi?id=365133
Bug ID: 365133
Summary: Consistency check failure: currency of a category has
no price set for 1900-01-01
Product: kmymoney4
Version: 4.8.0
Platform: Debian testing
On 01/03/16 01:32, Jack wrote:
I'm currently getting lots of message from the consistency check that I
do not have a stock price set on or before the opening date of the
account (presumably the account of the equity itself, not the investment
account.) In all cases I have checked s
On 01/03/16 01:32, Jack wrote:
I'm currently getting lots of message from the consistency check that I
do not have a stock price set on or before the opening date of the
account (presumably the account of the equity itself, not the investment
account.) In all cases I have checked s
I'm currently getting lots of message from the consistency check that I
do not have a stock price set on or before the opening date of the
account (presumably the account of the equity itself, not the
investment account.) In all cases I have checked so far, there is a
buy transacti
https://bugs.kde.org/show_bug.cgi?id=358935
--- Comment #1 from Jack ---
OK - I didn't look hard enough. Copy to clipboard and save as file are
available on the context menu (right clicking within the window). However, I'm
not going to cancel the bug, since explicit buttons for those items woul
https://bugs.kde.org/show_bug.cgi?id=358935
Bug ID: 358935
Summary: Tools/Consistency Check should allow save or print,
not just "OK"
Product: kmymoney4
Version: git master
Platform: unspecified
Am Donnerstag, 22. Oktober 2015, 11:28:41 schrieb Thomas Baumgart:
> > I think this error is not useful for the user. Mainly because the long id
> > is shown – to normal users this is the only place to meet this id, so it
> > is absolutely useless. We should change that (I can do that).
>
> Not re
[mainly changing the topic to my issues with Merrill Lynch in OFX
downloads]
On 2015.10.22 18:55, aga wrote:
On 22/10/15 19:47, Jack wrote:
On 2015.10.22 05:28, Thomas Baumgart wrote:
It would be extremely useful to know how you ended up there, as
this scenario should not happen in the firs
On 22/10/15 19:47, Jack wrote:
On 2015.10.22 05:28, Thomas Baumgart wrote:
On Wednesday 21 October 2015 21:08:36 Christian Dávid wrote:
>
> for a while now I receive such consistency check errors:
>
> * Transaction 'T000112' has a post date '
On 2015.10.22 05:28, Thomas Baumgart wrote:
On Wednesday 21 October 2015 21:08:36 Christian Dávid wrote:
>
> for a while now I receive such consistency check errors:
>
> * Transaction 'T000112' has a post date '⟨date⟩'
before one of
> th
Hi,
On Wednesday 21 October 2015 21:08:36 Christian Dávid wrote:
> Hello,
>
> for a while now I receive such consistency check errors:
>
> * Transaction 'T000112' has a post date '⟨date⟩' before one of
> the referenced account's openin
On 2015.10.21 16:55, aga wrote:
Hi Christian,
On 21/10/15 20:08, Christian Dávid wrote:
Hello,
for a while now I receive such consistency check errors:
* Transaction 'T000112' has a post date '⟨date⟩'
before one of
the referenced account's open
Hi Christian,
On 21/10/15 20:08, Christian Dávid wrote:
Hello,
for a while now I receive such consistency check errors:
* Transaction 'T000112' has a post date '⟨date⟩' before one of
the referenced account's opening date.
Referenced accounts: ⟨ac
On 2015.10.21 15:08, Christian Dávid wrote:
Hello,
for a while now I receive such consistency check errors:
* Transaction 'T000112' has a post date '⟨date⟩' before
one of
the referenced account's opening date.
Referenced accounts: ⟨account name⟩
Hello,
for a while now I receive such consistency check errors:
* Transaction 'T000112' has a post date '⟨date⟩' before one of
the referenced account's opening date.
Referenced accounts: ⟨account name⟩
The post date was not updated to
https://bugs.kde.org/show_bug.cgi?id=350903
--- Comment #5 from Thomas Baumgart ---
Created attachment 93951
--> https://bugs.kde.org/attachment.cgi?id=93951&action=edit
Result of consistency check with master version and the testfile attached here
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=350903
--- Comment #4 from Thomas Baumgart ---
4.6.6 is rather old. I cannot duplicate this problem with current master. In
master, the consistency check had been overhauled, that is probably why.
BTW: the correct fix would be to enter a price for AUD-EUR
ce of 1 AUD.
4. Edit the "Opening Balances (AUD)" transaction and change it to be a transfer
from "Bank Account" to "Cash Account" for 1 AUD with an exchange rate of 0.5
USD to 1 AUD.
5. Select "Tools | Consistency Check" and notice it now works fine.
--
Y
ou need
to do is open it, change the base currency and then run the consistency
check.
--
You are receiving this mail because:
You are the assignee for the bug.
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/k
https://bugs.kde.org/show_bug.cgi?id=350903
--- Comment #1 from Francois Marier ---
Created attachment 93853
--> https://bugs.kde.org/attachment.cgi?id=93853&action=edit
Error messsage after doing a consistency check
--
You are receiving this mail because:
You are the assignee for
https://bugs.kde.org/show_bug.cgi?id=350903
Bug ID: 350903
Summary: Consistency check fails after changing base currency
Product: kmymoney4
Version: 4.6.6
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Hi Graham,
On Thursday 07 May 2015 15:35:27 Graham Walton wrote:
> Since updating to KMymoney 4.7.2, every time I save my working file, I
> am receiving "consistency check reports" as follows:
> "The investment XXX has no price set for the opening date . Please
Since updating to KMymoney 4.7.2, every time I save my working file, I
am receiving "consistency check reports" as follows:
"The investment XXX has no price set for the opening date . Please
enter a price for the investment on or before the opening date."
I have one o
moved to another post date the price information
is moved along with it for investments transactions. This fixes the
reported issue, saving the file once will fix all price issues.
Also add the possibility to save the consistency check log to a file
or copy it into the clipboard.
Make sure that the
t date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consistency check log to a file
> or copy it into the clipboard.
>
> Make sure that
the
reported issue, saving the file once will fix all price issues.
Also add the possibility to save the consistency check log to a file
or copy it into the clipboard.
Make sure that the user enters a valid transaction date by checking
that the transaction date is after the opening date of each
/bugs.kde.org/show_bug.cgi?id=313793
>
>
> Repository: kmymoney
>
>
> Description
> ---
>
> If the transaction is moved to another post date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, savin
view request for KMymoney.
>
>
> Bugs: 313793
> http://bugs.kde.org/show_bug.cgi?id=313793
>
>
> Repository: kmymoney
>
>
> Description
> ---
>
> If the transaction is moved to another post date the price information
> is moved along with it
;
>
> Description
> ---
>
> If the transaction is moved to another post date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to sa
2015, 7:29 vorm.)
>
>
> Review request for KMymoney.
>
>
> Bugs: 313793
> http://bugs.kde.org/show_bug.cgi?id=313793
>
>
> Repository: kmymoney
>
>
> Description
> ---
>
> If the transaction is moved to another post date the price in
f the transaction is moved to another post date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consistency check log to a file
> or c
t; assignment to m_consistencyCheckResult does not happen. Now appending a
> > single line leaves the result with just that single line
> > (m_consistencyCheckResult.size() == 1).
> >
> > I suggest to override alwaysDisplayResult with 'true' in this case
with 'true' in this case to make
sure that the user gets a notification about the problem. Since
alwaysDisplayResult is false for those cases when the consistency check is run
as part of any File/Save operation it is even more important to make sure that
the user gets the information.
k
transactioneditor.cpp
> a215e3f8a1eaf2f7ccf1d73f29190f2ad86ff282
> kmymoney/kmymoney.h 92ab4b28d52c237222a2fb1106398ce0208215aa
> kmymoney/kmymoney.cpp c132983b63536e094375532082ea87c54461235c
> kmymoney/mymoney/mymoneyfile.cpp 8c1be4301a89b65f428edf2b8f0ab8b6e3dac51e
>
> D
ion
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consistency check log to a file
> or copy it into the clipboard.
>
> Make sure that the user en
reported issue, saving the file once will fix all price issues.
Also add the possibility to save the consistency check log to a file
or copy it into the clipboard.
Make sure that the user enters a valid transaction date by checking
that the transaction date is after the opening date of each and
. This fixes the
reported issue, saving the file once will fix all price issues.
Also add the possibility to save the consistency check log to a file
or copy it into the clipboard.
Don't allow the user to add a transaction before the opening date of
all accounts involved in the transaction.
estments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consistency check log to a file
> or copy it into the clipboard.
>
> Don't allow the user to add a transaction aft
; Repository: kmymoney
>
>
> Description
> ---
>
> If the transaction is moved to another post date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
>
ed along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consistency check log to a file
> or copy it into the clipboard.
>
> Don't allow the user to add a transaction af
scription
> ---
>
> If the transaction is moved to another post date the price information
> is moved along with it for investments transactions. This fixes the
> reported issue, saving the file once will fix all price issues.
>
> Also add the possibility to save the consi
price information
is moved along with it for investments transactions. This fixes the
reported issue, saving the file once will fix all price issues.
Also add the possibility to save the consistency check log to a file
or copy it into the clipboard.
Don't allow the user to add a transaction
.
Changes
---
Add a way to save or copy the consistency check log to make this fix complete.
Now the user has the possibility to look at the affected transactions and even
change the applied patch (i.e modify the account opening date instead of the
transaction date).
Summary (updated
hat but Jack also has a point. In the case of
> the file attached to the bug report the transaction date and the opening date
> differed by a few weeks. It sounds as changing the account opening date would
> be a better solution but it would be harder to implement since this is the
&g
hat but Jack also has a point. In the case of
> the file attached to the bug report the transaction date and the opening date
> differed by a few weeks. It sounds as changing the account opening date would
> be a better solution but it would be harder to implement since this is the
&g
ut Jack also has a point. In the case of
> the file attached to the bug report the transaction date and the opening date
> differed by a few weeks. It sounds as changing the account opening date would
> be a better solution but it would be harder to implement since this is the
&g
e of the file
attached to the bug report the transaction date and the opening date differed
by a few weeks. It sounds as changing the account opening date would be a
better solution but it would be harder to implement since this is the
transactions processing step in the consistency check. I was t
hich
> has an older opening date, should we fix that?
>
>
> Diffs
> -
>
> kmymoney/dialogs/transactioneditor.cpp
> 1aadc6fc96b7d21c7da198e92900023100fda9ad
> kmymoney/mymoney/mymoneyfile.cpp 8c1be4301a89b65f428edf2b8f0ab8b6e3dac51e
>
> Dif
28edf2b8f0ab8b6e3dac51e
>
> Diff: https://git.reviewboard.kde.org/r/122746/diff/
>
>
> Testing
> ---
>
> Opened the file attached to the report and observe that the consistency check
> fixes all of the issues.
>
>
> Thanks,
>
> Cristian Oneț
>
>
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
e file attached to the report and observe that the consistency check
fixes all of the issues.
Thanks,
Cristian Oneț
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
bserve that the consistency check
fixes all of the issues.
Thanks,
Cristian Oneț
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
On 2014.12.04 17:43, Cristian Oneț wrote:
2014-12-05 0:35 GMT+02:00 Jack :
Recently, I've been getting an odd message as part of the
consistency check when saving the file after downloading new
investment transactions. The message is "* shares set to value in
split of t
2014-12-05 0:35 GMT+02:00 Jack :
> Recently, I've been getting an odd message as part of the consistency check
> when saving the file after downloading new investment transactions. The
> message is "* shares set to value in split of transaction
> 'T009194&#
Recently, I've been getting an odd message as part of the consistency
check when saving the file after downloading new investment
transactions. The message is "* shares set to value in split of
transaction 'T009194'" (and I may or may not have enough
z
https://bugs.kde.org/show_bug.cgi?id=325441
Cristian Oneț changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=325441
--- Comment #4 from Thomas Baumgart ---
As Jack proposed: Please enter a manual price for the stock/investment in
question using Tools/Prices for the date requested in the warning message. To
reduce the number of messages popping up, turn off the auto-
013 19:48:35 +
> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=325441
>>
>> Bug ID: 325441
>> Summary: Consistency Check reports missing price
>> information on 9-2-2013; there are not transactions in my investment
>>
https://bugs.kde.org/show_bug.cgi?id=325441
Jack changed:
What|Removed |Added
CC||ostroffjh@users.sourceforge
|
On Sun, 29 Sep 2013 19:48:35 +
wrote:
> https://bugs.kde.org/show_bug.cgi?id=325441
>
> Bug ID: 325441
> Summary: Consistency Check reports missing price
> information on 9-2-2013; there are not transactions in my investment
> le
https://bugs.kde.org/show_bug.cgi?id=325441
--- Comment #1 from allan ---
On Sun, 29 Sep 2013 19:48:35 +
wrote:
> https://bugs.kde.org/show_bug.cgi?id=325441
>
> Bug ID: 325441
> Summary: Consistency Check reports missing price
> information on 9-2-
https://bugs.kde.org/show_bug.cgi?id=325441
Bug ID: 325441
Summary: Consistency Check reports missing price information on
9-2-2013; there are not transactions in my investment
ledgers for 9-2-2013
Classification: Unclassified
https://bugs.kde.org/show_bug.cgi?id=274018
--- Comment #11 from allan 2011-05-30 00:46:06 ---
(In reply to comment #10)
> I don't think it is really the dividend transaction that causes the need for a
> price. If it doesn't have a price, it can't calculate the value of the
> account. It d
https://bugs.kde.org/show_bug.cgi?id=274018
--- Comment #10 from Jack 2011-05-30
00:06:13 ---
I don't think it is really the dividend transaction that causes the need for a
price. If it doesn't have a price, it can't calculate the value of the
account. It doesn't make much sense to regist
1 - 100 of 111 matches
Mail list logo
