MP - Show Floated Weights in Rebalance UI
planned
A
Aquamarine Wolf
In model portfolios, I would like the ability to modify target allocations using the "Current Weight" rather than the "Target Weight" as the starting point. So the portfolio weights are dynamic. I tried to simply upload a csv with the current weights as a starting point, and it overrode all prior weightings for the portfolio.
TL;DR: I need a better way to adjust the model portfolio over time accounting for weighting movement based upon underlying price action.
Conor MacNeil
updated the status to
planned
Conor MacNeil
updated the status to
open
Conor MacNeil
Summary: When a user manually adds new allocation in the edit UI, they want the cells in the rebalance column to display the weights of the position, as per the rebalancing logic (daily, weekly, none, etc) as on that date. This could be an option (i.e, to display the target weight OR the floated weights).
Conor MacNeil
updated the status to
under review
Conor MacNeil
Hey Kyle, apologies I must have missed this one. You can upload dynamic weightings via the CSV and you can create custom rebalances in the edit portfolio window.
I am thinking of a few things here
1) Would you like the CSV upload to have an "append" option? I.e, only adds the new positions, not overwrites.
2) Did you know you can add new weighting allocations on specific dates?
Perhaps you can run me through an example or scenario to help me understand better.
A
Aquamarine Wolf
Conor MacNeil No worries - thanks for your reply.
1) Ideally, I would like to be able to upload a CSV that applies to a specific date. So the effect of your item (2), but done via CSV. Meaning all history prior to that date remains in place. When I've tried uploading CSVs, it wipes all history and becomes the only allocation. Maybe I'm missing something there?
2) Yes. However, the problem lies in the starting point when clicking on "New Allocation" for an allocation date. The weightings default to the last allocation weightings, but those have generally drifted over time since that last allocation date. I would appreciate the option to use current weights (rather than target weights from the last allocation date) as a jumping off point for creating the new allocation. When we are letting positions drift in a model, I have to edit every position in the new allocation to adjust for this drift. This adds some unwanted manual editing time. Again, my preference would be the ability to upload a CSV that would accomplish a new weighting on a specific allocation date.
Thanks for your help, happy to provide further clarification if necessary.
Conor MacNeil
Aquamarine Wolf: This is super helpful thanks.
1) On this point, you can upload dynamic weightings via CSV. The format looks something like (see image). You can get an example CSV by going to:
- Model Portfolios ➝ + Add New ➝ CSV Import
- In the top of the window there is an example CSV file.
The way CSV works currently is that every upload is an overwrite.
- You would need to include the historic weightings as well as the new ones to update the model, or add the new allocations by hand.
- We have had feedback that an append option would be valuable, and we may introduce that in the future.
2) For this point, I understand you.
Q: When you add new allocation, do you want the default weightings in the cells to reflect the weighting drift up until that date? I.e, show the weightings on that date if it had run without rebalancing until that date?
Photo Viewer
View photos in a modal
A
Aquamarine Wolf
Conor MacNeil Thanks for the quick reply.
1) Gotcha - thanks for that info. I guess I didn't realize the upload could cover multiple allocation dates. An append options does sound like it would be helpful, yes.
2) Yes, a default weighting reflecting the drift to that date would be my preference. I imagine not all users would run their models this way though, but having this as an option would be nice.
Conor MacNeil
Aquamarine Wolf: Thanks for taking the time to explain this, it really helps.
So for 1) it seems like we resolved that, but let me know if you have any follow ups there.
For 2) I am going to convert this ticket to a feature request and this conversation will provide the team they context they need. I may add some more context and pin it so it's more visible for us (Koyfin) and other users if they want to upvote it.