It looks like we found a problem with the currentDocument global object in xPages.
When the currentDocument is referenced inside a facet, it loses it’s reference when the page is refreshed. This occurs in both partial or full refresh.
It only happens once - the 2nd refresh it maintains it’s reference and does not lose it again.
If you are not using facet’s - it appears to work fine. It’s only when inside a facet. Of course - every single page in our system uses a facet. Ugh.
This was not occurring on 850. It only started occurring after we upgraded the server.
I can send a simple database to demonstrate this if you need it. But it’s pretty easy to duplicate. Create a computed field that shows a value from a field on the page using the currentDocument. Then have a button that refreshes the page (I just set a dummy requestscope). Change the field and click the refresh button. The value will be lost the first time you refresh. After that it will work. (obviously all this is inside a facet)
If anyone has found this problem and has a workaround - please let me know. Right now I’m debating the lesser of two evils - removing facets or removing the currentDocument references. Neither is going to be easy.