Forum Discussion

FaustoLiceaga's avatar
FaustoLiceaga
Qrew Trainee
3 months ago

How can I avoid saving a form if I need the user to create another record in a related table first?

Hi I need support with the following issue, I have created a form. 
This form contains a button to add more product requests. 
But many times users do not add products to the request and the request remains open and empty, unattended and incomplete. 

Until the user comes to upload products and in the form selects that no more products need to be added, Quickbase executes rules and notifications to complete this multiple or single product order as completed and processes the request. 

The problem is that I don't know of a way to prevent them from creating and saving the empty product order. Is there any way to achieve that result?

3 Replies

  • I know its been a couple months since you submitted this, but I had a similar situation today and thought I'd add my idea that worked for us. 

    You could consider creating a formula - checkbox field and name it "Product Request Validation" or something similar and have the field sit in the background of this form. Then create a form rule that says when the record is saved, if the box is checked, then abort the save and display a message that says "No Products Added" or something.

    Next create a summary field (also sitting in the background) from the child table where product requests are added. The summary field would total the number of records with the related unique identifier to this specific product request form. Then the formula - checkbox validator on this form will be unchecked for any time the summary field number is greater than 0.

    In theory, this would prevent your users from saving this form if empty, but allow it if product requests are entered.

  • I think I'm more fruitful approach will be to set up notifications and daily subscription reports to the record owner warning them that they have incomplete orders.

     

    you can also have large red morning messages on the header order record, warning them that they have not added any product

    • MarkShnier__You's avatar
      MarkShnier__You
      Icon for Qrew Legend rankQrew Legend

      In terms of the notification, obviously it would be annoying to the user to receive a notification every time the user saved the parent record. But you could have a pipeline which would use the clock step to wait to say 10 minutes, and then check if there were children added, and then, if no children added, it could update a field, which would trigger a notification, reminding the user to add products.