Databases
StackOverflow2013
Postsdbo
POUsing Multiple ModelForms with Class-Based Views
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Multiple ModelForms with Class-Based Views
    primarykey
    data
    text
    <p>I've got a situation where I'd like to add an additional modelform to my CreateView. We have an entry order system that allows someone to add an order and then add items to that order. Typically, when someone adds an order for the first time they'd like to also add an item to that order, so I want to combine those models into a single form and process them on initial order entry. I'm running into a problem when the forms don't validate. </p> <p>I've overridden get_context_data to add the item form to the template and I've overridden post to process the extra form. But when the forms are invalid I need to re-render the original form passing in the POST data. What's the preferred way to override get_context_data in order to render the forms with/without the POST data? Should I do something like this?</p> <pre><code>def get_context_data(self, **kwargs): context = super(OrderAdd, self).get_context_data(**kwargs) if self.request.method == 'POST': item_form = ItemForm(self.request.POST, prefix='item') else: item_form = ItemForm(prefix='item') context['item_form'] = item_form return context </code></pre> <p>Here's my CreateView in it's current form, where I'm currently stuck.</p> <pre><code>class OrderAdd(CreateView): model = Order form_class = OrderForm context_object_name = 'object' template_name = 'form.html' def get_context_data(self, **kwargs): context = super(OrderAdd, self).get_context_data(**kwargs) item_form = ItemForm(prefix='item') context['item_form'] = item_form return context def post(self, request, *args, **kwargs): order_form = OrderForm(request.POST) item_form = ItemForm(request.POST, prefix='item') if order_form.is_valid() and item_form.is_valid(): return self.form_valid(order_form) else: context = self.get_context_data() return render(self.request, 'form.html', context) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USscoopseven
    1. USscoopseven
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYour proposed `get_context_data` looks right to me, except that you have your if/else clauses reversed - you're trying to bind the item form only when the request was not a POST. Hmm. Except that then you create it twice and put an unvalidated copy into your context. I think I'd have `get_context_data` not insert the `item_form` value on POST requests, and instead add it myself after calling `get_context_data()`.
      singulars
      1. POUsing Multiple ModelForms with Class-Based Views
      1. USPeter DeGlopper
    2. COThanks, Peter. That was a copy/pasting mistake which I have corrected. What do you mean by "instead add it myself after calling get_context_data()?"
      singulars
      1. POUsing Multiple ModelForms with Class-Based Views
      1. USscoopseven
    3. COSince context is just a dictionary, you can add to or read from it outside `get_context_data`; see the answer I added for what I first had in mind, and then what I think is a slightly more elegant approach instead.
      singulars
      1. POUsing Multiple ModelForms with Class-Based Views
      1. USPeter DeGlopper
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload