We need to be able to share links to named versions of models, similar to the way Git works. Right now, all stakeholders including external investors see the head of the development branch, which effectively means we cannot make changes once the model link has been distributed.
1 Like
Thanks for the feedback! This will surely be a great feature to have and we have added this on our list.In the meantime, scenarios should make as a great workaround. Essentially the default scenario could work as the main branch and any additional scenarios could work as the sub branches. You can work on any on the scenarios without any effect on the default. When you are confident with your work on the new scenario, you can override it to the default, this will essentially work as a commit
While sharing the dashboard, be sure to create a view with scenario filters to prevent the viewer from accessing any unwanted scenarios.
Filtering out the dev scenario in a view and then sharing only that view would not work for Startup plan users. Dashboard users are able to see all views in the Startup plan. Sharing filtered views is only on the rather unaffordable Business plan, unless I am mistaken.
You’re right that permissioned views are only currently available on the Business plan. We’ll consider making this feature available to folks on the Startup Plan. In the meantime, we’ll be in touch to see if we can solve your problem here.
The more serious issue with the above solution using scenarios is that scenarios are quite limited in what you can do to the model. For instance, let’s say you want to move an input variable from the Sales Model to the Profit & Loss model. That is not possible with a scenario, which just allows modifying existing lines in the model:
A scenario is a variant of your model in which some variables have different values or formulas. The structure of the model — the variables, groups, and sections — doesn’t change across scenarios.
So we are really stuck with not being able to do any serious work once the model is distributed to even one important stakeholder, lest a change break the entire model. Modern software development is built on release pipelines: dev-test-production. Quite shocking that is not possible here.
A scenario is a variant of your model in which some variables have different values or formulas. The structure of the model — the variables, groups, and sections — doesn’t change across scenarios.
Scenarios are quite limited in what you can do, so I don’t view this as a solution. Modern software development is based on release pipelines. Quite shocking that this is not supported.
1 Like
Totally hear you Harold - we’ll surely consider adding this down the line!
1 Like