Hello,
haven’t uploaded recent changes in divvydiary for a while, I’ve just tried to do so from portfolio performance, but I am getting below error:
any idea ?
cheers
1 Like
@spartok - I believe the underlying problem is that I have changed the upload format to also include historic transactions (a feature request) but in some situations the DivvyDiary server does not like the created payload. I do not know yet what the problem is.
In the next version, I will write the payload to the error log. Then the DivvyDiary folks can maybe help.
In the meantime, if you are willing to send me your file to portfolio dot performance dot help at gmail dot com, then I can have a look. Maybe I see something in the payload that gives me a hint of what’s might go wrong.
2 Likes
Hi Adreas, thanks for quick reply
I’ve played a bit with my portfolio file, what I found is it did not like one specific security account of mine, others are working fine.
This security account is a special ‘french support’, in which fraction of share can be bought. In my case, it’s each month, on a standad nasdaq ETF
It seems divvydiary does not like this fractional share format.
Here’s the current overview of tx for this account (the oldest buy and sell were just to track previous value, before I switched to basic nasdaq DCA) :
And here a monthly buy example, with a fractional share buy:
I’ve made a copy of my portfolio file, and removed all the tx of this security account, except 1.
I only kept the buy on august 22, 2024, which is an entire number (314)
Then I retried the upload to divvydiary and it worked
So I believe issue is related to fractional share transactions !
cheers
2 Likes
Pinging @DivvyDiary
1 Like
@spartok Fractional shares are usually not an issue. The most common issue is a negative amount of shares in one of your transactions. You can send us the XML file to info @ divvydiary . com and we can debug the invalid transaction for you.
@AndreasB Writing the payload to the error log will be a great help in debugging these kind of issues. Thank you! If possible, additionally logging the response body would be a great debugging help, too.
1 Like
thank you for feedback
I do believe it’s linked to a recent pf performance update, as previously, with similar transaction on the ‘non working security account’, I was able to upload to divvydiary without any problem
hi,
can it be because “DUMMYTOTRACKSOAV” is a fake security, that I used just to track old stuff that are not so important
(so I created this security with DUMMYTOTRACKSOAV name, DUMMYTOTRACKSOAV ISIN and no quote
Yes, isin need to be a valid isin, if set, i.e. 12 characters length, only A-Z & 0-9
1 Like
thanks!
I just removed the ISIN and the error is gone !