I have a parent form (projects) in which I have embedded a child report (requirements). I want the child report to be a grid edit report us that users can quickly create and edit requirements directly in the parent form. However, I do not want to allow grid editing of the child report when the parent form is in view mode as the added records are then orphaned and not associated to the parent. I've tried a number of workarounds including required fields and not checking "Editable" in the field properties when the form is used for view but neither have produced a suitable solution.Is there a way to display the appropriate records from the child report as read only or as an image in the field when in view mode? Any input is appreciated.

I'm not sure I completely understand. Embedded reports marked "editable" but displayed on a view form will be the view version of that report. It's only on edit or add forms that it turns into a grid edit version. Do you mean then "Grid Edit" link that's on the embedded report?

Yes, the grid edit link is available and allows editing of the embedded report even when the the form is in view mode. When records are entered in this fashion they are not associated with the parent record which creates problems. I would like to prevent any method of creating orphaned records in the view mode of the form but still display the associated records in the embedded report.

No problem.Make a new form called "Dummy Form to Block Grid Edit". Put no fields on the form!Now that you have multiple forms, go to the forms settings and Forms usage and tell QuickBase which form to use for Grid edit - set that to be the Dummy form. So while users will still be able to get into Grid Edit, it will be a highly unsatisfying experience as there will be no fields to enter data into. hence they will not try again.

Nice "out of the box" thinking Mark. I like it!One step further: you could select the form usage for just that embedded report in case any other regular reports need to have their grid edit version still available.

Thanks for the quick reply. However, isn't this solution going to also prevent the users from accessing the actual grid edit form when the parent is in add/edit mode? In those modes I want the users to be able to grid edit.

Is there anyway to prevent grid edit report entries on a form in view mode but allow them in add and edit?

15 Replies

TomZ
Qrew Cadet
9 years ago
I initially went down the required field path but it was very cumbersome. The solution with the dummy form and one editable field might be the best one available.
MCFNeil
Qrew Captain
9 years ago
Is your "report link" field from the relationship, or did you make it on your own? Myabe check the target of that report link. Or include the proxy field for the [related parent] in the embedded reports.
EricMohlman
Quickbase Staff
9 years ago
I apologize for not being clear in my explanation yesterday. To demonstrate, I put together an example application and made the Everyone on the Internet group an admin in this app so you can access the settings.

If you view the parent record here: https://team.quickbase.com/db/bmk3z37je?a=dr&r=b you'll see an embedded report on the view form where the "Grid Edit" link is removed. To accomplish this, you need at least two forms on the child table: https://team.quickbase.com/db/bmk3z37jf?a=DFormList for the "Override role settings by report" option to appear. Expanding that section, you'll see that I selected "<Disable>" for the Embedded for Parents report. This specifically disallows that single report from utilizing Grid Edit, but any other table report has it as an option.
TomZ
Qrew Cadet
9 years ago
I was able to replicate this and as far as I can tell it's working as desired. This has been extremely helpful. Thanks again!

Forum Discussion

Is there anyway to prevent grid edit report entries on a form in view mode but allow them in add and edit?

15 Replies

Related Content

Preventing Budget Overrun

Preventing Scheduling Conflicts

Prevent save a record - New forms

Extract Date and Comment from prepend log entry field

Prevent Duplicate Entry from a Record Picker