<p>Could this be a reserved word? Generally I access fields using <code>entry.registeredOccurances</code> is there a reason you are using <code>fields[registeredOccurances]</code> and <code>entry[dateFieldHandle]</code>?</p>

CC BY-SA 4.0
2018-06-07T17:48:21.343Z
`fields[registeredOccurances]` is the correct name for the input, that's how you populate fields in post requests. You can access object properties in Twig with array syntax as well. Sometimes it's even necessary to do that. His error occurs because the default select fields are not supposed to have dynamic values. Since they can't be populated to "text". In the cp you would only see values from 0-xxx with his way because there is no label related to the selected value thus it's forbidden to do that. One has to dynamically change the options of the field before you can save such attributes
Robin Schambach
CC BY-SA 4.0
2018-06-07T17:51:01.120Z
thanks, I did not know that about craft. can you repost this as an answer to the question? I will upvote for you
Clark Nelson
CC BY-SA 4.0
2018-06-07T18:52:29.540Z
Thanks for your input guys. Do you think this is going to be achievable out of the box or will require a plug-in. I was hoping it would be very straight forward!
Mark
CC BY-SA 4.0
2018-06-07T17:28:12.690Z
2018-06-07T17:28:12.690Z
Clark Nelson
<p>I am trying to load some options in to a checkbox list from another entry so that a user and save select them form a checkbox list but I am unable to save the Entry Form with their selection.</p>

<p>I have created the <code>registeredOccurances</code> checkbox field in the Section, it has no options set as I want to set them on the entry form.</p>

<pre><code>&lt;input type="hidden" name="fields[registeredOccurances]" value=""&gt;    
    {# Load rows from SuperTable in to checkbox list #}
    {% for block in entry[dateFieldHandle] %}
        &lt;label&gt;&lt;input type="checkbox" value="{{ loop.index }}" name="fields[registeredOccurances][]"&gt; {{ block.date }}&lt;/label&gt;
    {% endfor %}

    {% if entry is defined %}
        &lt;p&gt;{{ dump(entry.getErrors()) }}&lt;/p&gt;
    {% endif %}
</code></pre>

<p>The dump is outputting the below, can someone help to interpret it?</p>

<p><code>array(1) { ["registeredOccurances"]=&gt; array(1) { [0]=&gt; string(33) "Registered Occurances is invalid." } }</code></p>

<p>Thanks for your help :)</p>

<entry><checkboxes><entry-form>
Entry Form: Populate checkbox list from another entry and save options in entry
# Entry Form: Populate checkbox list from another entry and save options in entry

(Asked by: username_0 on 2018-06-07)

I am trying to load some options in to a checkbox list from another entry so that a user and save select them form a checkbox list but I am unable to save the Entry Form with their selection.
I have created the registeredOccurances checkbox field in the Section, it has no options set as I want to set them on the entry form.
    
    {# Load rows from SuperTable in to checkbox list #}
    {% for block in entry[dateFieldHandle] %}
         {{ block.date }}
    {% endfor %}

    {% if entry is defined %}
        {{ dump(entry.getErrors()) }}
    {% endif %}

The dump is outputting the below, can someone help to interpret it?
array(1) { ["registeredOccurances"]=> array(1) { [0]=> string(33) "Registered Occurances is invalid." } }
Thanks for your help :)

**Tags:** entry, checkboxes, entry-form


---

## 1 answers

### Answer by username_1 on 2018-06-07. Score: 1

Could this be a reserved word? Generally I access fields using `entry.registeredOccurances` is there a reason you are using `fields[registeredOccurances]` and `entry[dateFieldHandle]`?

> **Comments:**
> **username_2**: `fields[registeredOccurances]` is the correct name for the input, that's how you populate fields in post requests. You can access object properties in Twig with array syntax as well. Sometimes it's even necessary to do that. His error occurs because the default select fields are not supposed to have dynamic values. Since they can't be populated to "text". In the cp you would only see values from 0-xxx with his way because there is no label related to the selected value thus it's forbidden to do that. One has to dynamically change the options of the field before you can save such attributes  
> **username_1**: thanks, I did not know that about craft. can you repost this as an answer to the question? I will upvote for you  
> **username_0**: Thanks for your input guys. Do you think this is going to be achievable out of the box or will require a plug-in. I was hoping it would be very straight forward!  

---

