This behavior is the same when calling a child (detail) edit form from the
nested list. No foreign key parameter is passed from the parent/master edit
form to the child/detail edit form, so the [Back to List] link results in the
same error.
I embedded a query call before the DisplayEditForm tag call, to obtain the
relevant foreign key value, but we shouldn't have to execute an additional
query to obtain the value.
Allowing us to append our own parameters to link calls will help a lot in this
area.
I would also like to see a label attribute for us to change the default [Back
to List] prompt. I think it might be confusing to the user on the
master-detail formsets where you have a list already embedded on the
edit/view/delete form.
Thanks,
Jeff
_______________________________
Jeff Fleitz
Tekquest, Ltd
Integrated Digital Solutions
http://www.tekquest.com
_______________________________
Jeff Fleitz wrote:
I have a master-detail edit form. When you Add a detail record and
click back to list without saving the Add, an error is generated because
the [Back to List] link just calls the originating edit form without a
primary key reference. I manually added the primary key as a url
parameter to the end of the DisplayListLinks add form and this one works
ok, because another parameter is not already being passed. This should
be generated by Plum, however.
<cf_DisplayListLinks
add="EmployeePhoneAddForm.cfm?EmployeeID=#URL.EmployeeID#">
Jeff
