Adding a required field to an in-use Custom Form

Hi @janepleadbeater,

Any new parameters you add to your basic intake info project form will go in as Null (unless you provide a default value, e.g. on a dropdown).

They will then be visible to end users (unless you put them within a special Parameter Section and restrict the View or Edit access to only certain users), and/or hide them (even if required) using display logic that then prevents them from being shown.

The next time end users attempt to save, any such new parameter that is both visible and required MUST be then provided in order for the save to complete.

Regards,

Doug

If your question is, "Will users who have filled out previous forms now be prompted to go back and fill out the new additional field?" the answer is no.

While technically by adding a new field to a custom form you are adding it to any project which had the custom form - the users have already completed the form - they will need to be instructed to go into the corresponding projects manually and manually add the new information.

I'm imagining a scenario where I update a legacy custom form and the system wants me to go and update thousands of prior projects - that would be not ideal.

To add on to what has already been mentioned, there is no way for "force" users to who have already filled out the custom form to go back and fill out the new, required fields. There will have to be some enablement and communication from you/your team to ensure this information is captured on historical projects. 

I'd recommend building a project report that has the name of the project in one column and all new required custom fields as columns and share that report out with appropriate users. Users will be able to in-line edit those fields without having to go into each project separately, and you can utilize column rules/conditional formatting to highlight any blank areas to ensure that everything is filled in.