How can I run through multiple documents where Store Form in Document is checked, to add a new field? I’d like to run an agent to add a simple field to these docs - I’m sure I’m missing something simple. thanks -Tony
Subject: Adding a field to a stored form
What you need to do is to tell Notes to ignore the stored from in the documents, so they will be processed with the revised version of the form in the design.
Run an agent on the documents that…
Creates a FORM field
Sets the value of FORM to the value of $TITLE (the name of the stored form)
Removes the $TITLE field from the document
Save the documents
Now the next time that document is opened, it will use the FORM to load the design version of the form to display it, and you see your changes. If it’s then saved, the new form is again stored with the document.
Subject: RE: Adding a field to a stored form
thats it Graham! many thanks-Tony
Subject: RE: Adding a field to a stored form
Hi,
It won’t work if the document purpose is to be send (it is the main stored form use), because no design will be found by the recipient…
ian
Subject: RE: Adding a field to a stored form
If you remove the stored form from a document, set the form field and then save the document again through the UI, I don’t see why this shouldn’t work.
Subject: RE: Adding a field to a stored form
Hi
A stored form is used to be sent to another user, and to be shown within his mailbox (any other use is a waste of time - except if you define a non-mail DB as recipient). It means that the destination DB does NOT contain the form design
If you wanna add a field to a stored form in the original DB, just change the design. [edit: PS, use stored forms in a single DB is a waste of disk space too…]
Please, explain me how you expect the recipient to change the design, according that he has not it on local.
Regards
ian
Subject: RE: Adding a field to a stored form
“A stored form is used to be sent to another user, and to be shown within his mailbox (any other use is a waste of time - except if you define a non-mail DB as recipient). It means that the destination DB does NOT contain the form design.”
I don’t know what lead you to believe, that anybody involved did not know that.
“If you wanna add a field to a stored form in the original DB, just change the design. [edit: PS, use stored forms in a single DB is a waste of disk space too…]”
Nope, I think you missed the point. The original question - as I undestood it - was: How can I update the design of a document that has a stored form. The answer is to change the form design, remove the info about the stored form and re-save the the document, which will apply the new design.
Discussion was not about why a stored form would be used in this case. You and I simply don’t know, if there is a reason to do so or not. Could be that it is just a waste (but still the question must be answered), could be that documents are routed back and forth between different databases in a workflow and now there is a design change, that should be reflected in all current documents. Pointing out, that this might not be needed is OK, but as I said: We don’t know for sure.
Subject: RE: Adding a field to a stored form
ok
you may be right.
Next time, i’ll ask questions before answering. 
regards
ian
Subject: RE: Adding a field to a stored form
I would also point out that stored forms in a single database can be effective if you use code that can modify the stored form. For example, since our Midas Rich Text LSX lets you add fields and rows with script, it is quite easy to have different stored forms with different fields and defaults, etc. I wouldn’t mention this if it were just true with Midas, but one of these days, somebody is going to start doing it with DXL, which is all native.
Subject: Adding a field to a stored form
Hi
You misunderstand something.
A document is a logical record stored in the database. It includes custom fields, and application ones.
A form ain’t nothing else that a way of displaying them.
You CAN store a new custom field in every document, you CANNOT change the way it’s displayed, unless you change the concerned form.
In your case, if the form is stored, you cannot change it, unless you create a new doc with a new custom form, then save it, then change the UNID, then delete the old UNID, and so on.
Depending on the purpose, you don’t really have to change the stored form. If you have, it means that the application is very badly designed.
HTH.