Thanks for the response Mike. I generally don't like it when a design has to change to fit a framework, however, in this case I decided to try your solution. I ran into a couple of problems though :-( 1) The fields that I'm looking up were required fields. Validation failed and error messages were displayed until I changed my model to not require those fields (which creates other problems I'd need to fix). Is there a way to hook in before validation? I over-road the model save function. Would the pre-save signal method fix this problem? Or maybe ModelAdmin.save_model? 2) The desired result of the lookup would be to display the change form so that the information could be verified. In other words, if doing the lookup, 'SAVE' (and 'Save and add another') should behave as if 'Save and continue editing' had been selected.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/26f88b4c-b2dd-4bce-aea7-d885295aa609%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
