Right now the system allows two changes with the exact same number within the same job and there is no way to prevent it. At least a warning might prevent some embarassing moments of sending the same change number twice
by: Jenna Y. | over a year ago | Project Management
Comments
Is there not a “require unique” option in the F7 window? Maybe this would require every single change order in the system to be unique, which wouldn’t work, but might be something to explore. Our company has changed the default change # to “NEXT by JOB” (type this exactly without quotes into the “Default Entry To” field), so it automatically will assign the next available change number for that job. Since this change, we have not had an issue with duplicate change numbers.