Skip to main content
Question

Form requirement nuanced trade-offs with proper relational structures

  • Jun 18, 2026 6:13 PM UTC
  • 2 replies
  • 114 views

Forum|alt.badge.img+9

I have two related questions!

Someone suggested using grid edit reports on my forms for a more all-in-one parent-child editable comprehensive form. That's not working at least on my end -- has anyone had grid reports be available within a form?

I'm reorganizing another section of my app for a division that hasn't moved over to my current setup yet. In their legacy setup, there is currently a one-form-fits-all, which requires many things based upon the service level they rendered. We're moving to a "Clients", "Cases", and "Service Calls" -- which means I no longer can require things at the Client or Case level based upon the extent of the service call..... is this just a trade off I have to make?  I'm concerned people might not go back into the parent record and update with additional information as it's received in this new setup (and hence why the grid edit would honestly be a fabulous option -- bring the Service Call record right onto the master record and edit it all from there).

2 replies

Forum|alt.badge.img
  • Observing
  • Jun 19, 2026 8:46 PM UTC

Are you using the legacy forms?  Because you can embed a normal report (not grid edit) in a legacy form using a Report Link field, and the form editor will have an "editable" checkbox option for the report field that turns the embedded report into a grid edit when editing the form.  Otherwise, if you're using both the new form style and the new inline editing reports, it also enables grid editing of the embedded report in the form.


Top Step
Forum|alt.badge.img+12
  • Observing
  • Oct 17, 2026 11:21 PM UTC

Bamber covered the grid edit part. On the second question, you don't have to give up the requirements. You move them to where the data gets entered.

 

Anything that depends on the service level belongs on the Service Call form. A form rule there can Require fields based on the service level picked, the same way your old one-form setup did.

 

For info that really lives on the Case or Client, roll the service calls up. Add a summary field on Case, for example a count of Service Calls where Service Level is the high tier. Then add a form rule on the Case form: when that count is greater than 0 and the field you need is blank, Require it, or use Prevent save with a message saying what's missing.

 

That only kicks in when someone edits the case, so I'd also build a "Cases missing info" report with the same condition and put it on the team's dashboard. That's what catches the ones nobody goes back to.

 

https://help.quickbase.com/docs/create-a-summary-field

https://help.quickbase.com/docs/create-a-form-rule