I figured out how to paste in a bunch of symbols to a fidelity dataset and update and it seems like I've got all the daily pricing data somewhere because I can see charts for them.

Now I would like to export those prices to an ascii file, but I can't see how.

I tried to install the ASCII Files Static extension in the extension manager. A green message says "Wealth-Lab restart required to finish installation." But when I close and reopen Wealth-Lab Pro 6.9, it's still not installed.

I would also like to load my Fidelity trade history so I can look at my historical trades against charts of historical prices. Is that possible? I see positions from all my accounts, but don't see a way to fetch trading history.

Thank you!

Oh, I found the restart button and now see an error. After I get prompted for admin password while WLP is restarting, I see some screens open and close, and a dialog box says "WealthLab.Extensions.Agent.Error. Server installation - Failed to create an IPC Port: Access is denied."

Ok, I hadn't noticed the maximum of 50 symbols for the export. But the export is to fidelity watchlists, which might not be what I want. I found the data files that seemed to have been generated from this and they were binary files.

Hi Sigfried,

Welcome aboard.

QUOTE:
Now I would like to export those prices to an ascii file, but I can't see how.

Before I show you how could you clarify why'd you to export the data out to ASCII files? What kind of task are you trying to solve outside of WLP by this? Maybe there's an easier way.

QUOTE:
I would also like to load my Fidelity trade history so I can look at my historical trades against charts of historical prices. Is that possible? I see positions from all my accounts, but don't see a way to fetch trading history.

This is an interesting new question. One forum thread per distinct problem please. Thanks in advance.

QUOTE:
Ok, I hadn't noticed the maximum of 50 symbols for the export. But the export is to fidelity watchlists, which might not be what I want.

Exactly, this isn't what you want. A totally different feature with similar name.

QUOTE:
Ok, I hadn't noticed the maximum of 50 symbols for the export. But the export is to fidelity watchlists, which might not be what I want.

No need to install the ASCII provider, it's already built in. But just in case, the IPC error is documented in the Wiki (Knowledge Base) here: Errors installing/updating Extensions > Failed to connect to an IPC Port: access denied

The reason Fidelity customer support referred me to Wealth-Lab was because I was asking how to export daily pricing data for lots of symbols at once and I asked if there was an API I could use. The reason I was asking that was because 1) I've been dissatisfied with Fidelity's charts for retrospectively reviewing my trading actions for a long time, and 2) I'm taking a graduate course in visual analytics and using the class project as an opportunity to start making the kind of charts I really want for evaluating my trading behaviors. My plan has been to make some relatively simple charts of sorts that I haven't seen before using either JavaScript (React and/or D3) or R, possibly with Shiny (Python is another possibility.) Since I've been directed to Wealth-Lab, it's possible that I could learn a lot about my trading behavior with it and without building my own custom charts. But at a certain point, I'm going to want charts that are unlikely to be available in any existing tool -- though they might possibly be easier to build in a programmable trading analysis application than on general purpose programming platforms.

Thanks in advance for whatever guidance you can provide!

Technically you could export data out of WL6 to ASCII files (or even some binary format) but your natural first step for building custom charts of your trading behavior is Wealth-Lab Pro:

Trade history to chart along with historical prices

QUOTE:
But just in case, the IPC error is documented in the Wiki (Knowledge Base) here: Errors installing/updating Extensions > Failed to connect to an IPC Port: access denied

The solution of running as administrator wasn't working for me. Besides the fact that running as administrator made the fonts go all wacky again; I couldn't open the extension...blah blah. Anyway, I just switched back to Windows after many years on MacOS. On my new laptop I decided not to give my regular login account admin permissions. I finally just made that account an admin, and I can install the Community Components Library without the IPC error now.

Glad you've got it sorted out.