Parsing json returned in django modelformset in template












0















One of the fields returned to my template in a formset generated by modelformset_factory() is a JSONField. I'd like to parse the json and display elements in it separately within the form, read-only.



This is readily done if I just return the queryset list, using a builtin filter I created, get(). But it has to be in a form that has some added fields for users to fill.



{% for foo in foo_list %}
<h5>{{ foo.json|get:"title" }}</h5>
{% endfor %}


The problem is that doing the same for a formset field I get the error "'BoundField' object has no attribute 'get'"



{% for form in formset %}
<h5>{{ form.json|get:"title" }}</h5>
{% endfor %}


Here is the filter:



@register.filter(name='get')
def get(d, k):
print('get(d,k):',d,k)
return d.get(k, None)


The relevant bits of the view:



...
foo_list = Foo.objects.all()
...
FooFormset = modelformset_factory(
Foo, fields = ['task_id','authority','dataset','place_id',
'authrecord_id','json'], form=FooModelForm, extra=0)
formset = FooFormset(request.POST or None, queryset=foo_list)
context['formset'] = formset
...
return render(request, 'datasets/review.html', context=context)









share|improve this question























  • But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

    – Daniel Roseman
    Nov 20 '18 at 22:41











  • I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

    – kgeo
    Nov 20 '18 at 23:45
















0















One of the fields returned to my template in a formset generated by modelformset_factory() is a JSONField. I'd like to parse the json and display elements in it separately within the form, read-only.



This is readily done if I just return the queryset list, using a builtin filter I created, get(). But it has to be in a form that has some added fields for users to fill.



{% for foo in foo_list %}
<h5>{{ foo.json|get:"title" }}</h5>
{% endfor %}


The problem is that doing the same for a formset field I get the error "'BoundField' object has no attribute 'get'"



{% for form in formset %}
<h5>{{ form.json|get:"title" }}</h5>
{% endfor %}


Here is the filter:



@register.filter(name='get')
def get(d, k):
print('get(d,k):',d,k)
return d.get(k, None)


The relevant bits of the view:



...
foo_list = Foo.objects.all()
...
FooFormset = modelformset_factory(
Foo, fields = ['task_id','authority','dataset','place_id',
'authrecord_id','json'], form=FooModelForm, extra=0)
formset = FooFormset(request.POST or None, queryset=foo_list)
context['formset'] = formset
...
return render(request, 'datasets/review.html', context=context)









share|improve this question























  • But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

    – Daniel Roseman
    Nov 20 '18 at 22:41











  • I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

    – kgeo
    Nov 20 '18 at 23:45














0












0








0








One of the fields returned to my template in a formset generated by modelformset_factory() is a JSONField. I'd like to parse the json and display elements in it separately within the form, read-only.



This is readily done if I just return the queryset list, using a builtin filter I created, get(). But it has to be in a form that has some added fields for users to fill.



{% for foo in foo_list %}
<h5>{{ foo.json|get:"title" }}</h5>
{% endfor %}


The problem is that doing the same for a formset field I get the error "'BoundField' object has no attribute 'get'"



{% for form in formset %}
<h5>{{ form.json|get:"title" }}</h5>
{% endfor %}


Here is the filter:



@register.filter(name='get')
def get(d, k):
print('get(d,k):',d,k)
return d.get(k, None)


The relevant bits of the view:



...
foo_list = Foo.objects.all()
...
FooFormset = modelformset_factory(
Foo, fields = ['task_id','authority','dataset','place_id',
'authrecord_id','json'], form=FooModelForm, extra=0)
formset = FooFormset(request.POST or None, queryset=foo_list)
context['formset'] = formset
...
return render(request, 'datasets/review.html', context=context)









share|improve this question














One of the fields returned to my template in a formset generated by modelformset_factory() is a JSONField. I'd like to parse the json and display elements in it separately within the form, read-only.



This is readily done if I just return the queryset list, using a builtin filter I created, get(). But it has to be in a form that has some added fields for users to fill.



{% for foo in foo_list %}
<h5>{{ foo.json|get:"title" }}</h5>
{% endfor %}


The problem is that doing the same for a formset field I get the error "'BoundField' object has no attribute 'get'"



{% for form in formset %}
<h5>{{ form.json|get:"title" }}</h5>
{% endfor %}


Here is the filter:



@register.filter(name='get')
def get(d, k):
print('get(d,k):',d,k)
return d.get(k, None)


The relevant bits of the view:



...
foo_list = Foo.objects.all()
...
FooFormset = modelformset_factory(
Foo, fields = ['task_id','authority','dataset','place_id',
'authrecord_id','json'], form=FooModelForm, extra=0)
formset = FooFormset(request.POST or None, queryset=foo_list)
context['formset'] = formset
...
return render(request, 'datasets/review.html', context=context)






django django-templates formset






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 '18 at 19:56









kgeokgeo

669




669













  • But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

    – Daniel Roseman
    Nov 20 '18 at 22:41











  • I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

    – kgeo
    Nov 20 '18 at 23:45



















  • But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

    – Daniel Roseman
    Nov 20 '18 at 22:41











  • I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

    – kgeo
    Nov 20 '18 at 23:45

















But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

– Daniel Roseman
Nov 20 '18 at 22:41





But this doesn't make sense. foo is a form, and foo.json is a field: it's a place for you to enter JSON in string format. It isn't actually JSON itself. What are you trying to achieve here?

– Daniel Roseman
Nov 20 '18 at 22:41













I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

– kgeo
Nov 20 '18 at 23:45





I was not clear; foo is in the first case an element in foo_list and foo.json is a json object. But that first bit doesn't involve forms. The problem is what follows - rendering the value of a BoundField in a template. I found the answer in an old patch thread - BoundField.value, described in my self-answer below. Thanks

– kgeo
Nov 20 '18 at 23:45












1 Answer
1






active

oldest

votes


















0














I found that applying a custom filter to form.json.value did the trick. The new filter converts that (text) value to json, from which I can do a get for specific keys.



new get filter:



@register.filter(name='get')
def get(d, k):
jd = json.loads(d)
return jd.get(k, None)


and its implementation in a template:



{{ form.json.value|get:"names" }}


BoundField.value is text, even though json in the db, so it needs conversion back for parsing.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400614%2fparsing-json-returned-in-django-modelformset-in-template%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I found that applying a custom filter to form.json.value did the trick. The new filter converts that (text) value to json, from which I can do a get for specific keys.



    new get filter:



    @register.filter(name='get')
    def get(d, k):
    jd = json.loads(d)
    return jd.get(k, None)


    and its implementation in a template:



    {{ form.json.value|get:"names" }}


    BoundField.value is text, even though json in the db, so it needs conversion back for parsing.






    share|improve this answer




























      0














      I found that applying a custom filter to form.json.value did the trick. The new filter converts that (text) value to json, from which I can do a get for specific keys.



      new get filter:



      @register.filter(name='get')
      def get(d, k):
      jd = json.loads(d)
      return jd.get(k, None)


      and its implementation in a template:



      {{ form.json.value|get:"names" }}


      BoundField.value is text, even though json in the db, so it needs conversion back for parsing.






      share|improve this answer


























        0












        0








        0







        I found that applying a custom filter to form.json.value did the trick. The new filter converts that (text) value to json, from which I can do a get for specific keys.



        new get filter:



        @register.filter(name='get')
        def get(d, k):
        jd = json.loads(d)
        return jd.get(k, None)


        and its implementation in a template:



        {{ form.json.value|get:"names" }}


        BoundField.value is text, even though json in the db, so it needs conversion back for parsing.






        share|improve this answer













        I found that applying a custom filter to form.json.value did the trick. The new filter converts that (text) value to json, from which I can do a get for specific keys.



        new get filter:



        @register.filter(name='get')
        def get(d, k):
        jd = json.loads(d)
        return jd.get(k, None)


        and its implementation in a template:



        {{ form.json.value|get:"names" }}


        BoundField.value is text, even though json in the db, so it needs conversion back for parsing.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 '18 at 23:51









        kgeokgeo

        669




        669






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400614%2fparsing-json-returned-in-django-modelformset-in-template%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?