Frans,

I remember that in old versions of LLBLGen Pro, a field was considered changed if its new value was the same as the old value. Isn't there a flag that toggles between the old behavior and the new behavior? I sure hope so, because I need the old behavior for my current project.

Thanks,

Jeremy

PS. I accidentally checked this message and can't uncheck it. Sorry.

No old behavior is present with a toggle. You can however use a combi of ForcedCurrentValueWrite and settign the field's IsChanged flag.

Ok, that should work. Thanks for the fast respose!

Frans, I understand how and why I should set the IsChanged flag for each entity field before saving, but why do I need ForcedCurrentValueWrite?

Thanks,

Jeremy

Jeremy wrote:

Frans, I understand how and why I should set the IsChanged flag for each entity field before saving, but why do I need ForcedCurrentValueWrite? Thanks, Jeremy

Because that method writes the value, no matter what. I forgot to add, you can also use the CurrentValue property of the field object, and use that. It will write the value as well and set the IsChanged flag for you as well (which should be even easier)