Thank you Chayce!
I definitely like route 1 better. From the parent table, 'Asset Form Request', when I edit the embedded report in Grid edit mode:
2. Also, until I save the 'Asset Request form' record, it doesn't have a record ID. So how do I ensure I can create within the Embedded form (Asset form) records for the related Asset Request form?
I am definitely missing something.
Deepa
If you're leveraging a basic relationship between Asset Request form and the Asset Form then you shouldn't need to do anything additional.
From the actual 'Form' or the Asset Request Form Table - you would just need to put the Report Link field that Quickbase generates by default on the form and have it set to a simple report that your users can grid edit. In the form elements - you can then make the element display as a grid entry and then when users are editing the native form, or when they're adding a new record Quickbase will automatically relate the new records as part of that functionality.
**I forgot to mention this - but this method only applies on the Legacy forms. The new forms don't have the same grid edit functionality as it stands right now to my knowledge so this technique is something the Legacy forms would be needed for.
Thanks Chayce.
I am using the new form and that does make things more time consuming for me as I am still figuring my way around those. It does allow Grid edits for embedded reports. But doesn't appear to automatically link the Asset Form Request record to the new asset forms via Grid Edit. I need to have to use the drop down in the Asset forms Grid Edit and select the Related Asset form and then the report shows up correctly.
Also now my app has both legacy forms and new forms making it inconsistent. Any way of switching back to legacy?
If you want to keep the new forms, I have a quirky idea that you could try to link them up automatically but if you're already on the fence between the two form types, I would personally switch over to the legacy forms so that this specific workflow is a little more seamless/user friendly with the grid edit.
You can switch your users back to the legacy forms in the form settings for each table. You'll have to make sure that any changes/updates that were made in the new forms are recreated in legacy, I'm not sure how difficult that would be for you though based on how you've used them thus far.
Qrew LegendJust chiming in on that Grid Edit issue where the current behaviour in new style forms allows the user to create children which are not linked to the parent or I guess if you make the [Related Parent] field required it would require the user to choose the parent that they are sitting on.
One option is to set the form properties in new style forms to disable grid edit. Then create a legacy form which is super mini in size. Just basically a heading which identifies the parent and an embedded grid edit report.
Then make a URL formula button for the new style form that would re-display the record Edit Mode on the Legacy Mini "Grid Edit" form.Then the user would do their data entry in grid edit mode and SAVE and it would re-display on the New Style form.
That would allow you to maintain consistency of look of the new style forms which in the long term is a better user experience but provides an acceptable workaround to Grid Edit where the user basically hits a button to Grid Edit.
Eventually one would hope that the New Style forms will mimic the Grid Edit behaviour of Legacy forms but until then this is probably an acceptable work around.
