%%Surrogate field problem

HCL Domino Domino Forum
1

I have a DB in production. Made a copy to DEV, modified the design as needed, pushed a replica of the DEV to the production server as a prototype for testing. Replaced the design of the production DB with the prototype DB after successful testing. In the production DB, there is a form that doesn’t work, but I cannot figure out why. It still works in the prototype DB.

Here it is in simplified fashion. I have a bunch of forms. In a subform I have a

that hides an “allow multiple values” dialog list field (so I can collect a list of selected items to submit with the form for processing with a WebQuerySave). This subform is included on every form on the site that requires processing. There was no change to this functionality in the recent design changes. It works on every form on the site except for one.

On the one form where it doesn’t work, it appears that the %%Surrogate field is not being generated for the dialog list field. ???

So, to recap…the code is in a subform, it didn’t change, it works on every other form in the database, and it works on all forms in the prototype, which is a copy of production with the same DB properties. I tried re-copying just the form that is not working from the prototype, but no luck.

So, what causes the %%Surrogate field to be generated (or in this case, not generated)? Any thing else anybody can think of that I can check? Nothing is being logged to the server log because it is not making it past the browser JavaScript validation.

Servers are 7.0.2, Windows 2003, patched to most recent. Designer Client is 7.0.2. Browser Firefox 2 (always) but also doesn’t work in IE.

This is fairly urgent as it is now broken in production. I did a workaround that allows them to process one at a time for the one form that is not working, but it is not pretty. I am also concerned that it could stop working for the other forms, which would be really, really bad.

Thanks in advance for any ideas.

2

Subject: %%Surrogate field problem

Michelle

Is there any chance that your form contains a field with the same name as the field on the subform?

Ben

3

Subject: %%Surrogate field problem - solution

Nope. The field is only there once.

In the big Duh! department, turns out the URL to get to the form (which is data driven) had been changed to ?ReadForm instead of ?OpenForm in the production database. (If I had had more coffee, maybe I would have noticed that quicker!)

So, for future reference, the %%Surrogate field is added only when the form is opened in Edit mode on the Web. (I am now properly caffeinated and can think.)