# as\_crispy\_field got passed an invalid or inexistent field

**URL:** <https://forum.djangoproject.com/t/as-crispy-field-got-passed-an-invalid-or-inexistent-field/21847>\
**Category:** Forms & APIs\
**Created:** [June 25, 2023, 2:37pm UTC](https://forum.djangoproject.com/t/as-crispy-field-got-passed-an-invalid-or-inexistent-field/21847 "2023-06-25T14:37:29Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [June 25, 2023, 5:07pm UTC](https://forum.djangoproject.com/t/as-crispy-field-got-passed-an-invalid-or-inexistent-field/21847/7 "2023-06-25T17:07:30Z")

</div>

Ok, that clears up a lot.

Personal recommendation - either use an FBV or create your own version of a CBV based upon the `View` class. The Django-provided CBVs are not really designed to work with multiple models. (Yes, you can get them to work, but it has always felt awkward to me.)

For a “link of links”, see my post at [Multiple Models to one Form - #2 by KenWhitesell](https://forum.djangoproject.com/t/multiple-models-to-one-form/18498/2)

In your situation here, I’d consider creating two model forms (with prefixes), one for each model. It’s probably going to be about as easy as any other method.

---

_[View the full topic](https://forum.djangoproject.com/t/as-crispy-field-got-passed-an-invalid-or-inexistent-field/21847)._
