Forum Discussion

ChristineK's avatar
ChristineK
Qrew Captain
4 days ago

Form requirement nuanced trade-offs with proper relational structures

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).

Relationships

1 Reply

  • Bamber's avatar
    Bamber
    Qrew Member
    3 days ago

    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.