Added computed fields, form not storing values in new fields

HCL Domino Domino Forum
1

I am not in sharp practive with Notes client apps so forgive me if this question seems super easy…

I have a notes app with some surveys in it - 5 years worth. The form was not programmed to do any math calculations and auto score the results with averages and such.

The developer also forgot to capture the entrants identity (gave them an optional editable field to identify themselves…) - so I am using $UpdatedBy to gather that.

I added computed fields, to gather averages etc., onto the field.

Theres seem to be applying fine, when I open an old survey, the converted values are there (slight conversion on the grading scale etc., ) and the math calculations are there.

The problem is I’d like thse computed math values to appear in the views as well, and they do not appear.

As I examine the document field properties, I see the newly added fields, are not present. They are computed fields, not computed fo display fields, but it is as if they are being treated as such.

So I can see them in drill down mode, but not in the view.

New surveys created with the new form - display in the view fine, and all the math calculations appear.

I am cautious to do a refresh documents agent because the $UpdatedBy will get my name in it then, causing another mess to clean up.

Also the date created was not captured to a field either so that is computed… and also problematic.

I tried creating a new form with the new values, setting it to inherit values from the selected document, and generating a new survey based off an old survey to pick up the values, calculate them and then have them stored in the form.

I was then hoping after this process to change the formanem back to thte original form, and hope all the computed values would be properly stored and accessible.

This rendered the same result…on screen in the document calculations appear, but in the view, they still dont appear and on document properties the new fields don’t appear.

If I manually, edit and resave the document by hand, the new fields are added and my name gets added etc., I can’t be doing that for 5000+ documents.

Any idea how I can get these new fields permanently ADDED and forced into the old documents with an agent that wont wipe out the original creation date and wont add me in the $UpdatedBy field or add the server - in that field?

2

Subject: Added computed fields, form not storing values in new fields

So, you want to update all of the documents, but you don’t want to be recorded in the $UpdatedBy field. Hmmm. That kinda gets around Notes security, doesn’t it? (It ain’t gonna happen.)

How about not worrying about the value of $UpdatedBy after your update agent runs, and simply use the current value?

3

Subject: Added computed fields, form not storing values in new fields

Run an agent that takes the last value of the $UpdatedBy and stuffs it into a new Computed When Composed field that you create on the form that records the user’s name. Use this field to display the author of the document in the view and then you don’t have to worry about the $UpdatedBy. Similarly, you can do this to a date field (or use doc.Created).

Your refresh agent should be able to run now without losing any of the information you still need.

4

Subject: RE: Added computed fields, form not storing values in new fields

Great idea Cesar.

I wrote some setfield agents to update the fields witht he values and this caused the document to store them.

Captured the creation and iriginal authors the same way and put them in other fields so i no longer have to reply on the hidden $ fields.

Thanks for the hlpeful response.