field is a string – a name of a field, field is not actually an attribute of row. You’ll need a template tag to get the attribute named field from row. This StackOverflow question may help you: https://stackoverflow.com/questions/844746/performing-a-getattr-style-lookup-in-a-django-template?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Mikkel Kromann Sent: Wednesday, June 13, 2018 3:54 PM To: Django users Subject: Nested for loops in templates Dear Django users. Thanks to the good advice of many people on this list, I've managed to create some nice generic class based views that work simultaneously with many models. The models may differ from each other with regards to the number of columns in their data tables as well as the naming of the columns. In order to use the same ListView template for many models, I will need to iterate not only over the rows of the queries, but also the columns. I managed to pass a field_list into the context_data - it works as it shows nicely in the table headers. However, when I iterate over the rows of the query result table, I'm not able to pinpoint the fields of the data row using the field iterator. My template.html is: <table> <tr> {% for fields in field_list %} <th>{{field}} {% endfor %} {% for row in row_list %} <tr> {% for field in field_list %} <td>{{row.field}} {% endfor %} {% endfor %} </table> Besides trying with {{row.field}}, I've tried with {{row}}.{{field}}, as well as {{ row.{{field}} }} (yeah, long shot ...) Any ideas, or should I try to create an entirely different data structure in my view, which can be parsed more easily by Django templates? cheers + thanks, Mikkel -- 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<mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com<mailto: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/c9e29d66-f93c-4fc4-ae9f-dbeae93a2e45%40googlegroups.com<https://groups.google.com/d/msgid/django-users/c9e29d66-f93c-4fc4-ae9f-dbeae93a2e45%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- 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/0c30ad68ef05474da124726df608820b%40ISS1.ISS.LOCAL. For more options, visit https://groups.google.com/d/optout.
