General

Re: Saving historic data input

Joern — Mon, 23 Apr 2012 05:48:54 GMT

Hello,

thank you for your thoughts.

Re: Saving historic data input

Anson Hidajat — Fri, 20 Apr 2012 15:00:17 GMT

Hi there,

Your current design is what I would recommend for you in your scenario. As long as you have a way to detect whether the opening form is the new vs. edit case, then switching to a read only view is a good best practice. Just make sure that the rule you are using is reliable meaning the field that the rule is based off will in fact be empty when you create a new form, but filled when you are editing the same form. Something like FormId usually will work. Hope this helps!

Saving historic data input

Joern — Fri, 20 Apr 2012 07:56:54 GMT

Hi All,

I'd like to wiretap your knowledge and experience :-)

I designed an IP 2003 form and provide the template on a SharePoint Services Site.

The user is doing his input in a couple of fields and then - by clicking a button - the form will be sent to the SharePoint library.

Usually, when the stored form will be opened again, it is possible to change the original input and save it again. I want to disable this so that the historic data cannot be changed anymore.

Therefore, I've designed the following rules for the button that is sending the form to the SharePoint library:

Setting the values of the input fields to read-only-fields in view 2.
Switching to view 2.
Sending the form to SharePoint library.

Now, when the form is opened again the View 2 is shown and cannot be switched.

Is this procedure lean, recommendable?

Thank you very much in advance for your hints and thoughts.