Pretty sure the answer is “no” as far as I can tell, in which case I suppose this would be more of a feature request. But it would be great if builders could bind an object set itself to a scenario such that scenario metadata follows the object set, and load/save operations are always applied to the scenario. Then widgets and functions could operate on them simply as object sets, entirely agnostic as to their scenario status, but with access to scenario metadata if needed via the object set’s API. Perhaps this could also enable builders to selectively apply (filtered) object (sub)sets of a scenario, instead of applying the entire scenario, similar to the selective publishing capabilities in Gotham.
1 Like