Our UX team have found a use case where we want to have a dropdown for dynamically populated items (i.e. it could be a combination of a variety of items in the system), and the user would be able to select one item at a time to rotate between different pages. Is there any sort of Nextworld functionality that can fulfill this?
Is it dynamically dependent on another table lookup value? There is an option for Table lookup data items to setup up a dependency. You can see this in action on Workflow Orchestration Definitions where Orchestrating Data Item field is dependent on Orchestrating Table ensuring that the data item is a field on said table in a drop down style UX.
Hmm I am not sure because it is data specific (item A, item B, item C entered). I would have to tinker around with it to see, thank you for the suggestion.
For more context: when we have a partially available item in a kit we have a splitting pop up display. We want the display to rotate between the backordered items in the kit and have a dropdown to go back and forth between the items if the user would like to do so.
I think it might. In the above, both TLs would need to exist on the application table. You’d likely need a TL to KitSelectionHeader and a TL for KitSelectionComponents with that dependent field defined as KitSelectionHeader configured on your popup . What I am unsure of is if you can limit that drop down by ONLY the backordered line items. It would likely give you a drop down consisting of ALL the components that Kit/Bundle has on it’s BOM
We are actually just using the kit as a template for component kits, so we do not need the header just the components. I see what you are saying though, I will give it a try. Thank you!
1 Like