I'd love to have the ability to create a list subset from a formula. That would give a great way to pre-filter and limit sparsity in modules.
Yes, this is a great idea @EarlC.
It's been requested multiple times here and is apparently on the product roadmap, but great to resurface this again.
Thanks for the link--I added my vote!
I agree that this would be easier to manage...but deleting elements from a subset is like deleting elements from a list..so all related input data would be lost.
Having this managed by a formula that could change from "TRUE" to "FALSE" dynamically, I find it a little bit risky.
I still prefer to have this in a more controlled way...especially for when the subset flag goes from "TRUE" to "FALSE" (deleting elements from subset).
The subset flag can be linked to a boolean formula, but not directly.
I would create an action that uses the boolean formula to update subset by launching an import into the list action.
I find this way more "stable" and less "risky".
What do you think?
I tend to agree with you here. There have certainly been times when I have thought "man it would be so much easier to manage these subsets if I could make them formula driven" but the risks you highlight are legit. I think the current setup encourages one to be a bit more contentious in the management of subsets and reduces the risk of inadvertent data loss from formulaic driven changes.
Should this functionality be made available, there will certainly need to be some strong best practices put in place to ensure models are built with integrity and auditability. I do think there are likely instances where module driven subsets could be powerful but the design will need to be considered carefully to taking into account for volatility in the output. An example we often see is where a list item may not be relevant to the current version (or even the previous version) but it was used in earlier iteration so if we had removed that item from the subset we would have inadvertently impacted a prior version of plan.
The inadvertent data loss is a good point, and something I had not considered--but is it any more risky than, for example, a scheduled import of a production list?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.