tag:infinitekind.tenderapp.com,2009-01-14:/discussions/suggestions/472-inconsistent-use-of-description-and-memoInfinite Kind: Discussion 2015-08-14T18:22:03Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262010-09-24T14:40:50Z2010-09-24T14:40:50ZInconsistent use of Description and Memo<div><p>I believe the correct way to fix this issue would be to change the name of the description field that is inside the splits to be a memo field. And then change the reports to only ever use the description field in the parent transaction (the one in the register not in the splits).</p>
<p>The downside of this approach would be that you could only have one description/payee per transaction even if that transaction contained splits. This is the way Quicken does it. Would this meet your needs?</p>
<p>Ben Spencer<br />
Moneydance Support</p></div>Ben Spencertag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262010-09-24T14:53:30Z2010-09-24T14:53:30ZInconsistent use of Description and Memo<div><p>Ben - Thank you for the quick reply.</p>
<p>I believe that your suggestion would fix the issue. The concern you raised (one description/payee per transaction) would not be a problem for my use.</p>
<p>I noticed another impact that hopefully would be resolved if you implement the change. Suppose you have a keyword you have included in each Memo field of single transactions and each Description field of split transactions. If you do a Search Report, specifying Combine Criteria OR and the keyword in each of Description and Memo, you will not get all the transactions. This is, presumably, due to the same issue. It would be great to have this fixed.</p>
<p>What's next? Might this be implemented? I'd be glad to help beta test, if that would help.</p>
<p>Thanks.</p></div>davidmbrowntag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262010-09-25T18:49:44Z2010-09-25T18:49:44ZInconsistent use of Description and Memo<div><p>I have created a ticket for this feature in our issue tracking system. I cannot promise when it it get implemented however I have taged showing that I personally think this is an important issue.</p>
<p>Sincerely<br />
Ben Spencer<br />
Moneydance Support</p></div>Ben Spencertag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262010-09-25T22:05:55Z2010-09-25T22:05:55ZInconsistent use of Description and Memo<div><p>Ben,</p>
<p>I'm glad you also see this as an important issue. It will add consistency and help people conduct proper searches. As I said, let me know if I can help in any way, which I suppose would be beta testing.</p>
<p>Thanks,</p>
<p>David</p></div>davidmbrowntag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-02-05T23:20:09Z2011-02-05T23:20:09ZInconsistent use of Description and Memo<div><p>Hello. I'm wondering if there is any progress on resolving this
issue as suggested by Ben in a prior post. I realize it's a
significant change, but I believe it would make for a more logical
use of the Memo and Description fields.</p>
<p>Thanks for any information.</p></div>davidmbrowntag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-02-12T05:23:31Z2011-02-12T05:23:31ZInconsistent use of Description and Memo<div><p>David,</p>
<p>We don't currently have any updates, but the feature request
ticket is attached to this discussion. By posting in this
discussion your interest in the ticket has been registered. This is
equivalent to voting for it. You will be automatically notified
when updates are available on this feature.</p>
<p>Please let me know if I can be of further assistance,</p>
<p>Angie Rauscher<br>
Moneydance Support</p></div>Angie Rauschertag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-02-28T03:13:56Z2011-02-28T03:13:57ZInconsistent use of Description and Memo<div><p>I would REALLY like this change too!</p></div>Erica Cartertag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-03-09T17:10:08Z2011-03-09T17:10:08ZInconsistent use of Description and Memo<div><p>Hello again. I just posted a month ago, but I would really like
to see this change implemented. I realize it's a very significant
one, so I imagine that it has many issues to be resolved. But I
have been doing significant analysis and reporting for a couple of
projects (I use Moneydance to manage the finances of a small
non-profit), and this inconsistency is causing me to need to spend
a lot of extra time manually sorting out reports generated my
Moneydance.</p>
<p>So, here's another big vote for this change. I'd be happy to
help beta test, if that is of use to you.</p>
<p>Thank you very much. Other than this, Moneydance is a great
product.</p></div>davidmbrowntag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-03-22T03:27:36Z2011-03-22T03:27:37ZInconsistent use of Description and Memo<div><p>My vote is AGAINST this change.... The way it current works, one
can have have multiple "payees" (using the description field) under
one transaction in the register. This is a function that was always
missing from MS Money, one that many user's (including myself)
requested for years...</p></div>dutchy999tag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-06-08T18:50:36Z2011-06-08T18:50:36ZInconsistent use of Description and Memo<div><p>Hi all,</p>
<p>Oh, Sadly I was incorrect. We're still working on how to
implement this.</p>
<p>My apologies,</p>
<p>Angie Rauscher<br>
Moneydance Support</p></div>Angie Rauschertag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-06-08T20:20:30Z2011-06-08T20:20:30ZInconsistent use of Description and Memo<div><p>Angie,</p>
<p>Too bad...I was excited when I saw your first message.
Moneydance is a great product, except for this inconsistency (that
and the fact that all reports aren't on one line, but for the time
being I get around that with the Find and Replace extension.) I
frequently export transactions to a spreadsheet for various
analyses. The way it is now, each column doesn't contain the same
type of data, depending on whether the transaction is split or not.
This requires a lot of manual work on my part that could easily be
implemented.</p>
<p>If I can be of any assistance, such as Beta testing, I suppose,
let me know. I'd be happy to help speed it along.</p>
<p>David</p></div>davidmbrowntag:infinitekind.tenderapp.com,2009-01-14:Comment/30869262011-08-11T17:13:04Z2011-08-11T17:13:04ZInconsistent use of Description and Memo<div><p>To those of you having problems with the inconsistency between
treatment of Description and Memo fields in split and non-split
transactions. This problem, and that of reports not being all on
one line, are solved with the excellent and free extension, Find
and Replace. This extension gives you powerful capabilities to
extract data, based on flexible criteria you specify, and copy the
resulting report to a spreadsheet for further analysis. Reports are
on one line and (by selecting the Splits as Memo's option), both
split and non-split transactions are exported consistently.<br>
Give it a try. And if you like it, drop Kevin, the developer a line
to tell him. He recently added the Splits as Memo's option by
request.</p></div>davidmbrown