You probably know, @cculber2, that our data aggregator, Yodlee, can provide investment “holdings” information to our backend when those accounts are linked in the Console. Long ago, when we ran data feeds via the old “feedbot”, we offered core sheet called
Position History that updated with this information.
When we rebuilt the data feeds to work via the add-on, the change delivered many important customer benefits, but one thing that was lost was the
Position History core sheet.
I know some of the team, including @Peter, are keen to bring back holdings data at some point (given the need which you acknowledge).
One challenge that is slowing us down (along with the many other important stories in the engineering pipeline) is settling on a standard for the report. In other words, if we are going to populate this data set again, how do we standardize the output out of the gate to give it the most runway for all the many potential customer uses?
Position History format is mocked up here. It functioned a lot like the
Balance History sheet with a row for each holding for each day. A challenge with this is the massive proliferation of data and the challenge of building performant templates to digest and summarize the data; the Net Worth template is the closest analog and can be cripplingly slow with many linked accounts but imagine 100’s of holdings updated daily with formulas trying to render that data set on a monthly or weekly basis… (So, is it best to always append new data? Or should the report just overwrite with the latest position— i.e. more performant, but unable to track history?)
I can’t make any promises on the prioritization in the engineering pipeline (which @heather manages), but, if you have insights or suggestions on what would be helpful from a core sheet & reporting perspective, that could help unstick the reporting.