You also might be able to do something either at the FORM level or post save pipeline level by using the parent-child relationship to store the number of "child items" are presently saved and tied to the parent. (#-Children).
Then in the Parent-Child relationship besure to include both the Parent Status and #-Children
Remember that a detail record doesn't count as saved until it is saved, so your detail form PREVENTS save before saving with the parent status = approved and the #-Children = x.
I think the challenge here is that the Add Record is being done in Grid Edit.
ah.. sorry. I missed that entirely. So yeah - Pipelines seems to be the "best" way to fix it - though preventing it prior to save... is another thing entirely.
You could also send the "offending" user an email at the tail end of the pipeline - though it's probably more hassle to setup - but it might be worth it. Or - what about blasting the user a CHAT via a chat interface - e.g. "Hey, you can't add or delete items from 'X' ! "
@Mark Shnier (Your Quickbase Coach) & @joe vandervest thank you for your comments.
What I did so far:
I created 2 separate Report Links to be used in Form, and using Dynamic Form Rules different reports are visible.
It still allows user to go into "Grid Edit" or "Open Full Report" but at least they will not be able to easily add it when editing form.
Next steps:
One more time thanks for contribution to this problem solving 💪💪
------------------------------
Adam Krzyzanek
------------------------------
