I also see the behavior that you do, and agree that it’s weird. What I’m not sure about, though, is if overriding the field metadata is meant to be used with new rows like that, although I don’t know why it wouldn’t be able to. I’ll go ahead and log it as an issue.
Typically, when people want to specify a value in a field on a new row, they’ll do it either through the action framework somewhere, or in an action under the model. However, I can see for date fields that you can’t set them to be a value from another model. I think that’s a shame (and I actually wanted to use that functionality as well just the other day) so I’ll submit a request about it to the product team.
Thanks!
