T
Teri
I have a bunch of records that I want to keep in a Forms Library. I want
that each time someone submits an update - through an InfoPath Form - each
version of the Form is kept so we have an audit trail of changes. How do I
a) set a field in an InfoPath Form to require a unique field? (e.g. That
application name is already in use.) and b) get each Form to create a new
listing, not override the existing listing? (I realize these sound at odds
with each other, but I would have the submitters add a number to the
Application Name to create the new listing but reference it back to the
existing one.) e.g. application ABC is already in the Forms Library. The
owner of application ABC submits an update to change the description. In the
form, they'd enter application name as "ABC 2", along w/ the desc change.
The admin would then see it pending approval and approve the change. In the
Forms library, both the original Form submitting ABC and the update Form
submitting ABC 2 w/ the new desc would be in there for history.
that each time someone submits an update - through an InfoPath Form - each
version of the Form is kept so we have an audit trail of changes. How do I
a) set a field in an InfoPath Form to require a unique field? (e.g. That
application name is already in use.) and b) get each Form to create a new
listing, not override the existing listing? (I realize these sound at odds
with each other, but I would have the submitters add a number to the
Application Name to create the new listing but reference it back to the
existing one.) e.g. application ABC is already in the Forms Library. The
owner of application ABC submits an update to change the description. In the
form, they'd enter application name as "ABC 2", along w/ the desc change.
The admin would then see it pending approval and approve the change. In the
Forms library, both the original Form submitting ABC and the update Form
submitting ABC 2 w/ the new desc would be in there for history.