Huge Oversight with New Forms?
Hi,
Maybe I'm missing something, but I just ran into an error with the new forms and am baffled as to how we are about 7 months into the new forms and this error exists.
I've setup a very basic p...
Forum Discussion
Are you still having this issue? or have any updates?
------------------------------
LB
------------------------------
I submitted a ticket with Quickbase support. The the inability to chain-add children records on the new form, according to Quickbase support, "is working as designed". So that wasn't great to hear. I've had to implement custom buttons to account for this. Though the other issue with the new forms is you cannot hide the native "Save" button. Even with adding &IFV=1 to the url, it still shows in the upper right corner, whereas the old forms would properly hide it. So now I have 2 custom buttons and a blue save button in the upper right corner I don't want and doesn't work.
As for the issue where saving the parent puts me in a loop, they've escalated my ticket to get this addressed.
Both the parent and child are in the new forms, so a difference in form style is not the issue, unfortunately.
------------------------------
Curtis Middleton
------------------------------
There's an exception to the rule for that parent and child forms must both be on new-style or both on legacy-style.
Scenario: You are editing a previously save record in a new-style form and you want to add a parent with the pop-up-then-refresh method. That works if the pop-up uses a legacy-style form, but not if it uses a new-style form.
Same is true if you use %%rid%% on an unsaved new-style record to which you are adding a parent.
Alex WilkinsonCurtis - would you be willing to share the formula you are using to place a Save + New button on your child form? I understand the native Save button will still show, but the additional button would be helpful for my scenario.
Thanks
