System-generated fields like id, created and updated are enforced strictly to have that/those field type and name. For existing databases, adding an alias field to such fields would allow remapping the field to another field.
Limitations?
- Data type for the field would need to be of the same underlying type; otherwise, it would throw a type conversion error.
- For now, generation of the fields values would still be enforced by Mantis.
System-generated fields like
id,createdandupdatedare enforced strictly to have that/those field type and name. For existing databases, adding analiasfield to such fields would allow remapping the field to another field.Limitations?