Computed when composed fields change on web doc when doc saves ? Query_String

HCL Domino Domino Forum
1

I have a very basic form that I open on a web browser through a link and pass a couple of values through the url → window.open(‘doc2?openform& | & dateTime3.DateOnly & |&| & dateTime1.TimeOnly & |’, ‘_self’);|

The form has a computed when composed Query_String field, and a date and time field that get their values from parsing the

Query_String. So good so far, it works great.

A sample Query_String would be:

openform&%2004/25/2003&11:00:00%20AM

and the form opens with the following:

Date 04/25/2003

Start Time 11:00:00 AM

Perfect.

Now I need to save the information, so I have a save button on the form (action button). I’ve tried it two ways, with a @command([FileSave]) and I’ve written a lotusscript agent that will read the document.context and create a new doc. They both work the same BUT the Query_String and any variables I have that read from it change and garble when saving, even though they are computed when composed and should be cast in stone. Query_String turns into this mess during the save:

OpenForm&Seq=1&%2004%2F25%2F2003&11%3A00%3A00%20AM

and my fields pick it up and parse it as best they can, which does not produce valid date formats anymore.

Why oh why does Domino taunt me so?

I was able to create fields to parse the second version and use the first just for display, but I’m confused by this. Does it consider the saved form to be a new form again and gives it new computed when composed values?

2

Subject: That is the way it works and here is how to fix it…

Create a second computed when composed field and have that field reference the query_string field and either just copy over the value or do your parsing of the query string. Then that second field’s contents will not change.

Howard