This post is only important to those who create computed fields in progeny.  That should really just be study coordinators and possibly a very few highly responsible individuals who communicate such field making/changing with the study coordinators.

If you need to change an existing field into a computed field in progeny, please start the computed field as a completely new field and delete the old one rather than changing the field type on an existing field.  When you change the field type of an existing field to a computed field it will cause a database error.  The field won’t work and it will interfere with things like how the individual or sample data sheets are displayed or how LIMS actions/reactions that utilize that field work.  If it happens, we just need to delete the field everywhere that it is referenced, so it isn’t the end of the world, but it is better if we just avoid the problem all together!  Thanks.