-
I have random intermittent save conflicts, which of course all have a $Conflict field. I have a View whose Selection Formula is along the lines of (is an error) | @IsAvailable($Conflict). Far as I know this has been working using R6.x for years, but since save conflicts haven’t been a problem, only (is an error) documents have been appearing.- Enter R8.5.1FP1 HF472, which is a specific version that MUST be employed because HF472 is the ONLY way to fix a serious bug in XPage attachment processing, and R8.5.2 is a non-option. The good news is the application seems to be working overall, and quite well. The bad news is the many, many, many changes for XPages appear to have introduced this intermittent save conflict issue.
-
The worse news is the View no longer lists conflicts, so while I checked it numerous times during testing and since deployment, it’s been lying to me about their existence, and the users had to complain before I found out. Very not good. Ideally I do all the complaining for my users! (bemused grin)
-
I also don’t appear to be able to FT search using [_Conflict] or FIELD _Conflict. Query is understandable, it simply refuses to function correctly, either returning all documents in the database, or none, without regard to $Conflict.
-
I should point out that some users are using the web/XPages, and some are using Notes R6.5.5, while we transition them over. So far it’s been only the Notes users that generate conflicts, but they are currently the lion’s share of all possible users, so that could be simple statistics.
-
I searched here and found nothing relating to the $Conflict field itself. Zillions of save conflict issues with XPages, even some of my own, but nothing else. If I missed it I apologize, but I did try.
-
Does anyone else see this, and does anyone have any suggestions how to identify only the save conflicts in the system? I’d like to get an idea of how rampant this is.
Thanks for your time…