Hello. Setting default values for a form linked to a “modify object” action usually works fine. Today, it’s telling me no parameters are configured when they are, in fact, configured. See screenshots attached. It says “No allowed parameters” but there are allowed parameters. I’ve set up this type of actions many times before so very keen for help to figure out what’s different this time. Thanks.
Hi,
It seems that the UserAccessMachineObject is now set to “Allow multiple values” (I noticed this in the function code). The Parent Org Id parameter might be expecting a single object reference by default. This setup works when UserAccessMachineObject is a single object, but now that it has become an array, it doesn’t qualify as valid input because it’s no longer clear to the action which one object should be used to retrieve the default value from.
Is there a specific object from the multiple UserAccessMachineObject entries that you would like to use to set the default value? You could perhaps pass that in separately as a single object parameter
1 Like
Hello, yes it seems this is the problem: the “set default value” only works if you disable the “allow multiple values” option.
In other words, you cannot pull the current values of multiple objects to use an action to edit those or different properties in bulk.
So my feature or solution request would be:
- Minimum: Better error message for that one as I think specifying “multi-selection not compatible with default values” would be more clear
- Ideal: Ability to natively have default values with multi-selection enabled (I say natively because I learnt you could technically do this in a workshop with a typescript function today).
Thanks for your quick response!