tag:infinitekind.tenderapp.com,2009-01-14:/discussions/moneydance-development/2886-possible-bug-with-split-transactionsInfinite Kind: Discussion 2020-10-20T03:40:23Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/484760792020-07-21T03:35:32Z2020-07-21T03:35:32ZPossible bug with split transactions<div><p>I'm using MD 2020. I was attempting to load a transaction into an Investment account to handlle non-security related fees. So I"m using Parent/Split. I was going crazy because the parent tx was being created with an amount of 0 and the default Category, that is, the split info was being lost. It took forever to figure out that I had to set the split.description for it to work (even if I set it to an empty string). Is this a bug?</p>
<pre>
<code> s.setAccount(feeAccount);
s.setAmount(txnAmount, txnAmount);
s.negateAmount();
// above fails without a description
s.setDescription("");</code>
</pre>
<p>The absolute only difference in the code between a working split and one that fails is the presence of the setDescription. If I comment that out that line, it doesn't work.<br>
I haven't included the code that creates the parent and synchs it but I'm happy to include it if that helps diagnose the problem.</p></div>Bob B