Bug:Field Type Not Required When Adding Field via Admin UI

[Abhinegi2]

Previously, when adding a new field through the Admin UI, the type (or dataType) field was mandatory. It was not possible to save the field without specifying a type.

Currently, it is possible to save a new field by just entering the label and leaving the type undefined. This causes an invalid configuration to be saved in the database, which later breaks report generation and other dependent logic (e.g., deserialization errors like missing creator parameter dataType).

Steps to Reproduce:

1. Go to the Admin UI.
2. Add a new field (e.g., in Child or any other entity).
3. Only provide the field label and leave the type field empty.
4. Click Save.

[sleidig]

Oh, do we know how we lost this required flag?

[Abhinegi2]

When a new field is added and the _id is auto-generated, duplicate f_ids are also getting saved.
So the issue is that somehow SchemafieldForm validation is not working properly whenever the field ID is autogenerated