Add Annotation

[Galassi_Stefano]

It's possible add fields annotation via script in data modeller?
Best Regards

[wlandgraf (Wagner Landgraf)]

Yes, you can use customization scripts for that:

Customization Script

[Galassi_Stefano]

Hi,
where can I find a complete list of the parameters including the various properties (TCodeTypeDeclaration etc.etc)
of the procedure OnColumnGenerated, OnAssociationGenerated ..
??
Best Regards

[wlandgraf (Wagner Landgraf)]

Unfortunately we don't have such reference yet. For now you have the code completion tool in the script editor and our support to help you out.

[Galassi_Stefano]

what I would like is to take the information from the definition of the fields or table (for example from the description) and create the validation annotations with the script language.
I can do it?

[wlandgraf (Wagner Landgraf)]

Yes, it's possible. There are a few examples in the documentation and here in Support Center that you can use as a base and extend it for your own use.

Example on adding an atribute based on some field information (name):

Scripting Language Info

My beginning of automaticly create a column procedure OnColumnGenerated(Args: TColumnGeneratedArgs); begin if Args.Field.Name = 'FsngCreate' then Args.Field.AddAttribute( 'Column(''sngCreate'', [])'); end; procedure OnClassGenerated(Args: TClassGeneratedArgs); begin Args.CodeType.AddField( 'FsngCreate', 'TDateTime', mvPrivate); end; The FsngCreate field is created, but t…

Adding property/field based on field information:

Mysql Datetime column generated instead of Date type

Thanks Wagner, One last question: Is there any documentation or source code about these scripts other than datamodeller_manual.pdf? For example TGDAOField. Also I put the following code into script in order to convert every Date field even if I forget to override in the mappings. But documentation will be very helpful. procedure OnColumnGenerated(Args: TColumnGeneratedArgs); begin if Args.DBField.DataTypeName = 'Date' then begin // What about the required fields then this is a wrong ove…

Actually an example of adding validation attributes based on some field information:

About Aurelius 5

Hard to believe. When I read the new documentation I thought it would naturally lead to a DataModeler upgrade. It would be far better than mantaining dozens of columns this way: procedure OnColumnGenerated(Args: TColumnGeneratedArgs); var LTipo, LCampo : string; begin LTypeName := LowerCase(Args.CodeType.Name); LFieldName := Lowercase(Args.Field.Name); if (LTypeName = 'tperson') then begin if (LFieldNam…