"Initialized" property is not nulable, so the dataset considers it as a required field. It's an error at dataset level, not aurelius manager level. You can just declared the property as Nullable<boolean>, or set the Required property of the TField to false.
I said in the post before, but just to make clear, it is not a database field, is a regular class property.
Actually, is a property from the base class of my entity. What I am understanding is that if Aurelius can map because recognize the data type, it map on the dataset EVEN it is not marked as a database field.
I see that properties that are PROTECTED does not get mapped. that is fine
However not all PUBLIC properties are correct. Not basic types (like lists, or my own types) are not listed on the dataset, that is eventually ok.
Interface type are listed. But as required, however does not cause any problem.
public properties with types AureliusDataset can handle are displayed. If they are not nullable, the TField is marked as required. For better control of what you want to display on the dataset, always define the persistent TField's, as you would do with any dataset.
Well, it should define the field as not required. But as I said, you can always define a persistent field and remove the required. Or set a default expression. If you want send me a compilable project that reproduces the problem, I can check it here why the nullable property still creates a required TField.