Users need to be able to track their pedigree seeds variety separately. Previously in FM PRO they could name their own inputs but we need to think of a workaround to meet their needs if we aren't going to allow that.
My client suggested the following: If there was a way we could add an option to a harvest activity to mark if it's being stored as pedigree, then allow the user to add a crop certificate # and then after it's recorded we add a new activity for "seed cleaning", and then when a user cleans their seed they can pick that stored pedigree input and finally assign it a lot #.
Thomas Chevalier
