Hi, I'm trying to pass data across a quick create/postInsert boundary, that is, I'd like to set a flag on the entity to conditionally run some stuff in

postInsert

. My initial attempts seem to indicate that values set on

this

as well as virtualAttributes are zero'd out (the entity instance on which the values are set, is not the entity instance on which the postInsert is called). Is there a mechanism for this? Am I mistaken in understanding the above behavior?

I think when we do this we use a

property

with

persistent=false

seems to get zero'd out (set to empty string), doesn't make it across the jump into postInsert

I'm not sure I've seen the behavior you're describing about things getting zeroed out. When is the value intiailzied and when is it set to an empty string?

well, default initialized, to an empty string

you can slap a

default

on the property definition

yes, but the goal is not to have a default, but to have it set to the value it had, before postInsert

I don't follow what you're trying to do

yeah we do don't we ... that does work ... so there is a way

you'd have to

create({ 'prop' : val })

with that I get an, probably due to the persistent=false

The [...] attribute was not found on the [...] entity

with

ignoreNonExistentAttributes=true

it doesn't throw, but the value is always set to the default, rather than the value in the create(...) call

yeah I think I have a bug in on github about nonpersistent attributes being ignored by create from a while back

i guess conceptually

create

is a static member method