Why is TColumnProp.Required on so many fields?

[wlandgraf (Wagner Landgraf)]

@Rohit_Nz

In some cases there are default values, so I don't need the user hassled that they have not entered a value.

Again, this is not user related. This is database information indicating the database field is NOT NULL.

@Rohit_Nz

I am also puzzled by NoInsert, NoUpdate.

This is by default for generated identity fields. You can always change it, either manually or automatically using Data Modeler scripts, examples:

Appending error

You can import it using TMS Data Modeler and remove the TColumnProp.Required from the list of column properties using customization script. For example: procedure OnColumnGenerated(Args: TColumnGeneratedArgs); begin if Args.DBField.FieldName = 'Dummy' then begin TCodeSnippetExpression(Args.ColumnAttr.Arguments[1].Value).Value := '[TColumnProp.NoInsert, TColumnProp.NoUpdate]'; end; end;

Property permission in Xdata (SwaggerUI)

You can do that via customization scripts. Example: procedure OnColumnGenerated(Args: TColumnGeneratedArgs); begin if Args.DBField.FieldName = 'CreationDate' then begin TCodeSnippetExpression(Args.ColumnAttr.Arguments[1].Value).Value := '[TColumnProp.NoUpdate]'; end; end; If you want different DTOs (classes) for different endpoints, then in this case you need to effectively create different DTO classes for each endpoint.