Prior to market open, the Account Balances window displays the wrong prices for the "Last Price" column, see screenshot. Hitting the Update button doesn't fix the problem.
If the market
is open and streaming updates are enabled, this isn't a problem if you stream updates constantly. If you stream updates
some of the time, it can be a problem even when pressing the Update button. The Update button will not correct the Last Price when it's wrong.
One important comment. I don't typically have streaming updates enabled, so when WL was started prior to market open, it was
not enabled. But enabling it and pressing the Update button when the market is closed will not correct the Last Price column. What I would like to see is the Update button correcting the Last Price column even if the market is closed (or open). Is it possible to do that? Right now, the Update button doesn't correct the Last Price at all.
Size:
Color:
I understand what you're saying, but this would be a departure for how streaming is used in Wealth-Lab Pro, i.e., only during market hours. I personally don't see a problem updating the Accounts tool with the last-traded price even if pre-market, but, for example, we wouldn't want to be triggering premarket in the Quotes tool. Changing where the market hours time filter is employed could be a problem for getting what you want here.
Re: The Update button will not correct the Last Price when it's wrong.
If you're referring to within market hours, I'll check on that.
Size:
Color:
QUOTE:
If you're referring to within market hours, I'll check on that.
Yes, that's a problem; the Last Price column isn't always updated during market hours when streaming is disabled and the Update button is pushed. If I'm not mistaken, there are circumstances when it "might" be updated. What I can say is that it's never been a problem in WLP 6.9.20.7.
Size:
Color:
I thought I would clarify that turning on Streaming Updates (for the Account Balances window) does effectively cause the Last Price column to "eventually" update, but only after the next tick. And I think that's the correct design and behavior.
What doesn't happen (in WLP 6.9.22.7) is the Update button fails to force a Last Price column update when depressed whenever Streaming Updates is disabled. I can post other examples if you need them. This was not a problem in WLP 6.9.20.7.
Size:
Color:
Let me add, the "Positions value:" number on the Account Balances and Positions window doesn't agree with the Fidelity website either. Please fix that too. This was not a problem with WLP 6.9.20.7. This is probably a computational artifact to the "Last Price" column not being updated correctly, Post# 1.
I hope a fix is coming soon.
Size:
Color:
Re: Wealth-Lab Pro Positions Value.
It looks to me like Wealth-Lab Pro gets the "Current Value" of the positions (correct when enabled Streaming Updates), but in the use case I'm observing, it doesn't take into account the "Margin Debit Balance" for purchases [and probably sales] today. The effect is that WL Pro is double-counting the value of a [long] Position on day it's entered. We'll see what we can do.
Re: Update
I think the answer is just to use Streaming Updates for now. There's a new Streaming Provider integration underway for Wealth-Lab Pro, so we'll try to knock out the Update button at that time. Since you have to log in to use WL Pro now, maybe the way to move forward is to remove both of those buttons and stream those updates automatically (that's just one guy's opinion for now).
Size:
Color:
QUOTE:
I think the answer is just to use Streaming Updates for now. There's a new Streaming Provider integration underway for Wealth-Lab Pro
Thanks for that suggestion and the update. True, I don't typically use streaming updates for the Account Balances and Positions window. I only stream Charts and the Quotes windows. For those windows, the current streaming provider
works fine for me, although ...
... I do get lots of these messages in the error logs:
CODE:
Please log in to see this code.
Size:
Color:
Thanks for the log. We'll check it out. A ticket with the reference to this post might be helpful, but I'm already tracking it otherwise.
Size:
Color: