<p>I just did some testing of this. I thought I noticed the same thing, but then realised that I created and added the field to my section (a single) only after it already existed. In that case the defaults didn't show. But then I added the field to a channel section and created a new entry and the defaults show in that case.</p>

<p>So I think the reasoning is that it won't populate defaults on an already existing entry as these could easily go unnoticed by someone editing and end up being saved to the entry when unintended.</p>

CC BY-SA 3.0
2017-04-27T15:35:14.797Z
Interesting find Mike!  Thanks for doing that :)  Yes indeed that makes sense and the only thing I did not test was a new entry.  So the odd part than I guess is that Matrix with a Table field works as expected.  Good to know.
Vin
CC BY-SA 3.0
2017-04-27T15:37:15.893Z
Well, you can think of a new matrix block as a type of new "entry" anyway (programatically in Craft, they are just another type of element), so I think it follows the logic I've laid out.
Mike Pierce
CC BY-SA 3.0
2017-04-27T15:39:11.300Z
Makes perfect sense.
Vin
CC BY-SA 3.0
2017-04-27T15:28:25.790Z
2017-04-27T15:28:25.790Z
Mike Pierce
<p>I have built a few fields with the Table field.  I noticed an odd behavior maybe it's normal, but want to check.</p>

<p>I use a Table field with defaults entered, the defaults do not show up.  Now for the odd, if I put the Table field in a Matrix field, the defaults show up.  Is that normal Table field behavior?</p>

<table-field>
Table field type defaults
# Table field type defaults

(Asked by: username_0 on 2017-04-27)

I have built a few fields with the Table field. I noticed an odd behavior maybe it's normal, but want to check.

I use a Table field with defaults entered, the defaults do not show up. Now for the odd, if I put the Table field in a Matrix field, the defaults show up. Is that normal Table field behavior?

**Tags:** table-field


---

## 1 answers

### Answer by username_1 on 2017-04-27. Score: 1 | Accepted answer

I just did some testing of this. I thought I noticed the same thing, but then realised that I created and added the field to my section (a single) only after it already existed. In that case the defaults didn't show. But then I added the field to a channel section and created a new entry and the defaults show in that case.

So I think the reasoning is that it won't populate defaults on an already existing entry as these could easily go unnoticed by someone editing and end up being saved to the entry when unintended.

> **Comments:**
> **username_0**: Interesting find Mike!  Thanks for doing that :)  Yes indeed that makes sense and the only thing I did not test was a new entry.  So the odd part than I guess is that Matrix with a Table field works as expected.  Good to know.  
> **username_1**: Well, you can think of a new matrix block as a type of new "entry" anyway (programatically in Craft, they are just another type of element), so I think it follows the logic I've laid out.  
> **username_0**: Makes perfect sense.  

---

