I’m currently building an aviation app and ran into an issue while working with Workshop Scenarios.
My use case is to create a “Work Package” inside a scenario and then compare scenarios to evaluate their impact on flights.
However, I’m having trouble when trying to use components that allow selecting an object created within a scenario (i.e., not yet in the ontology). I can see the object in the dropdown and select it, but the selected object never loads afterward.
At this point, I’m not sure where the issue is coming from:
an ontology issue
an action/configuration issue
or a limitation of Workshop itself
Specifically, I’m wondering: Is it actually possible to select and use an object that still exists only within a scenario (not yet applied to the ontology)?
For comparison:
I can select objects that already exist in the ontology without any issue
Once I apply the scenario, the object becomes selectable and works as expected
But before applying the scenario, I’m unable to use it
Has anyone encountered this behavior before, or can confirm whether this is expected?
The Object Dropdown widget doesn’t support scenarios. That’s it. It can show scenario objects in the list, but the moment you select one, it tries to resolve it from the real ontology, and fails because the object doesn’t exist there yet.
Your options:
Swap to an Object Table — it’s scenario-aware (has the “Load data from scenario” setting). Use it as your selector instead.
Apply the scenario first, then select. Annoying, but it works.
Store the object’s ID as a string variable from the creation action and pass that downstream instead of the object itself.
You’re not doing anything wrong, the widget just isn’t built for this.
Felipe Montes
Development Advisor
Follow me @ linkedin.com/in/felipemontesl/ or GitHub: Brazillianerd
The cleanest path is probably the “apply scenario first, then interact” flow, even if it feels clunky. Here’s why:
The Gantt, like the Object Dropdown, almost certainly resolves objects from the base ontology, so any widget depending on a selected scenario object will break if the scenario isn’t applied first.
The string ID approach only works if the Gantt accepts a loose ID parameter, which is unlikely without a proper object binding.
Orphan records are a real risk if scenarios are never properly applied or discarded.
Practical suggestion: Structure the Workshop so the user applies the scenario first (clear, prominent action button), and only then unlocks interaction with the Gantt, you can use conditional visibility on downstream widgets, blocking them until the scenario is active. This avoids the confusion without creating dirty data.
The Ontologize video on the World Cup simulator might show a UX pattern for exactly this worth checking before ruling it out.
