Right, I have hit a weird problem I don’t remember hitting before! This is on a “WEB” form…
I have a form, the form has a computed subform using a formula. Now if we take this scenario…
If a field contains “A” load subform A, else load subform b
Nothing tricky there!
So I have an editable field whose default values computes to A or B.
I create a new document and the field computes to “A”, and subform “A” loads
I refresh the document using a button and viewrefreshfields…
The field still has the value “A”, but the subform has switched to show subform “B”
Doesn’t make sense at all… I’ve been looking at this so long now I’m probably looking over the problem and not at it!
Subject: Computed subforms on web, bug?
The document is reloaded, but Field does not really contain a value yet (from the back-end perspective). The default value is not re-evaluated. This should result in subform B being loaded.
Subject: RE: Computed subforms on web, bug?
I appreciate that the value won’t be stored in the backend. You see the problem was noticed when saving…
Domino must re-compute the subform before it saves. It was noticed that some fields from subform A were not there (they do not exist on subform B) which is kind of how I ended up testing the refresh idea which also causes the same problem.
Now I have a copy of the same system, on a 6.5 server that has been working for a couple of years. The new one was on a 7.02 server.
So I took a copy back to R6, checked and they both report a R6 ODS, yet the new one still doesn’t work but the existing one does.
I have tried making the field used to drive the computed subform computed, CWC, CFD etc… nothing seems to work. After the first refresh the subform is wrong. If I save the document, edit again the correct one is loaded and from that point on it is OK.