Hi,

LLBLGen allows adding new custom properties to a generated entity.

These properties also show up for example in a grid in data binding scenarios.

But they are not part of the edit cycle in data binding. For example when editing a row and then pressing ESC before committing the changes: all LLBLGen properties go back to the original value but the custom properties don't.

As well field level versioning works only with the LLBLGen properties but not with custom ones.

Is there anyway to make custom properties part of the edit cycle and of field level versioning? If yes how would I do that please?

Thanks, Patrick

But they are not part of the edit cycle in data binding. For example when editing a row and then pressing ESC before committing the changes: all LLBLGen properties go back to the original value but the custom properties don't.

Would you please explain your databinding setup in details? Win or Web? Are you using a BindingSource / LLBLGenProDataSource?

As well field level versioning works only with the LLBLGen properties but not with custom ones

I think Field Level Versioning is designed around the EntityFields of the Entity not its properties.

Walaa wrote:

Would you please explain your databinding setup in details? Win or Web? Are you using a BindingSource / LLBLGenProDataSource?

Win & Binding Source

Walaa wrote:

I think Field Level Versioning is designed around the EntityFields of the Entity not its properties.

Yes I think so too but I would still like to make my custom properties fully part of the entity so I was hoping to find some answers here.

Thanks, Patrick

There is no way to do this simply because the custom properties are generated into the code by the designer.

The intention of custom properties isn't for you to change the fields, after all where would they be persisted given they don't map to any specify table in the data store.

If you wanted to set up a generic name value pair mechanism to associate with your entities, that's certainly possible. You could define the table structures and through LLBLGEN generate appropriate entities. The value fields of the name value pair could then be versioned as an EntityField in the same way this works for other entities.