I regularly use embedded views but am suddenly seeing something happen I’ve not encountered before.
Users are finding documents appearing in an embedded view (which uses Show Single Category) that do not belong to the parent form. Hitting refresh corrects this, but users have no idea they are the incorrect documents in the first place.
This is not limited to any particular event (read vs. edit) and can happen at any time. In some cases, users have been looking at the parent doc and literally see the view refresh and suddenly contain incorrect documents.
This is a known issue in your release. The problem is that the category calculated by your formula is converted internally to a position within the view, e.g. it remembers you have selected the 56th category. If a new category is created that appears in the view above the category you are viewing, then when the view auto-updates it will show you the new 56th category, which was #55 previously.
If you can arrange to have the view sorted in such a way that new categories go to the end, that would help; otherwise, I think you can turn off the view auto-update in the view properties. This might not help if users are editing documents in the embedded view, however, since it will reload to redisplay their changes.
This Notes “bug” which was supposedly fixed in R5, and then revisited and supposedly fixed in R6, has now made its way into a system where we are using a 7.0.2 client. The db has been working fine for years, and now all of a sudden we have users experiencing these same results… but I guess I shouldn’t be surprised :o(
The problem and solution will most likely have to do with your view selection formula. Are these response documents to the document you are looking at? What is the formula for the view selection? Can you paste the formula here? Is it possible that the formula may be broad enough that these documents meet the criteria for the view?
DocA: This is the “parent” document which includes the embedded view.
DocB: This is the “child.” It should be noted that this document is not a Response doc in the truest sense, meaning that it is not designated as such in its design.
DocB can only be created from DocA. When this happens, a unique ID from DocA is carried over to DocB. The ID is stored in a field called “Code” on both forms. The embedded view on DocA is marked to Show Single Category, with the category being the “Code” field.
The view is categorized by Code and the only criteria for the view is Form = “DocB” & Status = “Active”
Based on using Show Single Category, this should limit what appears to only those DocBs that were created from DocA. At least, that’s how it’s worked the dozens of other times I’ve done this.