Hi,
Is there a way to leave the default selection of a subnm blank to force the user to select something? Otherwise even tho the parameter is required it either captures the default or first value.
We don’t have an OOTB feature in UX to enforce a blank selection on open. But I think by going beck to how you would solve this in Excel/TM1Web will work equally well in UX for regular dashboard or process popup.
Just create a dummy element which doesn’t have any data called “please make a selection” and include it in the subset or MDX which fills the subnm list and set “please make a selection” as the default value.
Not the most elegant thing ever and you need to create dummy elements in the model. But it will solve the requirement.
Yes but this will still allow the user to run the process, meaning the process button will be active.
I’ll create an ER for this if it’s possible achieve.
Ahhh. You mean you want the value to be blank on open but the subnm to have required=true so the run button remains inactive until a value is selected?
You probably don’t need to bother with the ER. I’m told this is already in develop branch (and already available in FPM specific branch of UX as is multi-select subnm)
Yes precisely! Thanks.
Coming back to this thread, @Ulas did you implement the workaround mentioned above by Scott, or is there a new feature in UX that solved the above?
We have a similar request, but with the added requirement that the process button should be greyed out (unclickable) if not all of the required parameters are selected/filled in. Any recommendations on that?
This is the default behavior in UX, unless subnm is used, but that’s also my request.
I haven’t done any workaround on this, so it’s a good question for @cw-ch-scott or @tganz
This is cool feature! 
Yes, I agree, having an option that forces all parameters to be mandatory would be great!
One way to solve using a mix of this workaround without having to add a dummy element, is is to have the the subnm option list starting with a consolidation like “All Products” (or you create the dummy element as Consol), and add a validation on this parameter that only level 0 is valid (you can also add level 1, 2, etc). This way will force the user to select something and the button will be disabled at first.
Using the advanced option below:
"validation": {
"Level": {
"valid": [
1,2
],
"message": "Please select a product Category!"
}
}
In my example the “All Products..” is not a valid option, but the elements underneath are:
Hope this helps!
2 Likes