We have some fields on the form that are computed for display. Later down the form we have another field that is computed for display as well, and it is a Hotspot. This hotspot should only be display if both the computed for display fields have a value.
What is happening is if the user opens the form, they see the Hotspot, however when they switch to edit mode, the hotspot disappears, but if the user presses f9 to refresh, the hotspot comes back.
I could put a uidoc.refreshHideWhens in the Post Mode Change, however this causes the screen to flash.
Also, If I change the computed for display fields to computed, there is no issue as weel, but I don’t want to store these fields in the document.
Has anyone else had this issue with Hidewhens and Hotspots, and if so, how did you fix it.
We tried that oo and once again it did not work. As it turns out, some forms do work. I haven’t come up with a good explanation, but it seems that notes does something firstm probally the hide-when and then does the computation of fields.
Hide formulas are evaluated immediately before the fields on the paragraph they’re associated with. Once a hide formula is evaluated, the result is remembered during the rest of the form processing. For efficiency, if the same hide formula is used again on a later paragraph, the stored result is reused – even though, in the meantime, the fields it refers to might have changed their values.
If the above does not solve your problem, we need more information about what you’re doing. If you’re not sure what information to supply, the C R I S P Y document might help you.
I should have posted this in the Version 8 forum, since that is what we are running with, I was a little too quick when I posted it.
The problem is that we are basing our hide when’s on computed for display fields. The values of the computed for display are NOT being changed. So when we open up the document, we can see our Hotspot (this is hidden if the computed for display field is blank). However when we switch to edit mode, the hotspot gets hidden, but if the user refreshes the document by pressing F9, the hotspot shows up again. It does not happen to all forms. So for example if you delete the tab table, and open up the form, the hotspot shows in read and then again when you switch to edit mode. We ar enot sure if the form has lots of hide whens it gets lost on what to display.
Naturally, if you open the document in edit mode right away, the hotspot stays.
Another issue, but not large is that open up in Read, hotspot is there, switch to edit mode hotspot goes away, press F9, hotspot shows up, process Control E to go back to read mode, hotspot stay there, process control E to go back to edit mode, Hotspot stays there.
The problem is that we are basing our hide when’s on computed for display fields.
The fact that it works on other forms proves that this is not your problem. I’ve tried it myself and I don’t have any difficulty there. The fact that they are CFD might be a factor, because of differences in when they are calculated vs. a Computed field, for instance, but in the situation you described, I don’t see why the field type should matter.
Please read my last post carefully and think about whether this might be a factor in what’s happening. Look at all the hide formulas ON the paragraph containing your CFD fields and BEFORE that paragraph.
Since you hope to be CRISPY, I think you should note that one of the top recommendations is that you post your source code.
I note you responded to David that the line you’re trying to hide is on a subform. This is possibly relevant. Please consider whether there are other helpful facts you’re not telling us.
Add an always-hidden line at the beginning of the subform, and see whether that helps any.
What would happen if you took the Computed For Display fields out of the picture and based the Hotspot’s “hide when” on whatever logic those fields are using instead of those fields themselves?
Not sure if that would solve anything or not.
What happens if you move the Hotspot to the very bottom of the form outside of any tables and what not? Same result?
wish we could, however this is a shared sub-form, so the hide when’s are different for each form, which is why we based them on computed for display fields. The hotspot must stay at the top of the form, since they use this to link back to the main document. Like I said before we have a work around, it is just not very pleasant.
Are you sure that one of your fields wasn’t “originally” a computed field? If the field type was originally computed and a document was saved then the value will be saved to the underlying document. When you open the document (in read mode) the value will still be retained and the computed for display formula will only change (overwrite) your original value when you go to edit mode.
Just for grins try looking at the document properties from the view and see if your computed for display field actually shows in the list of fields (2nd tab). If the field is even listed in the document properties then you’ll have to write an agent to clear those fields from existing documents.