This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
You have my vote. I know this was already discussed in length when they initially announced the Input() function. What you're trying to accomplish can be done by separating actions and grouping them, when in fact, as you suggested, just allow Input() to work on the action "Add rows to another table"
Still not supported? HOw convenient would it be if a user clicks "Add" in a child table, but instead of being redirected to a form, a pop-up just shows up allowing the user to supply the needed information for the new item being added to the child table.
If we could use INPUT() already in the first action (add a new row to another table using values from this row), then by clicking CANCEL, no new row would be created.