I have a single category embedded view in one of my forms. It works flawlessly in Notes 7.0 installed on machine A.
The view does not display on machine B that has Notes 8.0.2 installed. There is a ‘category not found’ message in the status bar. This issue seems to be associated to my particular client as others who use Notes 8.0.2 do not have this problem.
Any ideas on what is happening?
Subject: It’s a data issue
“Category not found” indicates the value used as the category selection key does not match any available categories in the view. However the key is being calculated or chosen, on your particular workstation, it doesn’t deliver the expected result. If you can view the embedded view in designer and check the selection formula hopefully you will be able to figure out what’s wrong.
Subject: Continues not to work
The view is a categorized view of document UNIDs that are stored in a computed field called MainID with the default value:@Text(@DocumentUniqueID).
It still makes no sense to me why it works (and has for a couple of years) in one client and not in another??
Subject: Is it the same ID file on both clients or different ID files?
If different, then I would suspect reader fields. The the ID file that works on the other machine.
Subject: Same ID file on both clients
Hi,
It is the same ID file on both clients
Subject: are the docs visible to you by other means
On the pc on which you’re getting the ‘category not found’ msg - are you able to view the documents that you’re expecting to see in the embedded view if you access the view directly? Is this db on a server or is the problem occurring with a local copy?
Subject: You have to see what the single-category formula is returning…
I’d suggest you look really hard at the single-category formula of the embedded view. If there doesn’t seem to be anything wrong with it, please look again more carefully. It must be calculating a UNID somehow. Where is it getting the information to calculate the UNID? What makes you think it must match a view category?
It’s actually rather odd that you would have a view that’s categorized by the UNID of the documents in the view, since that means each category would contain only one document. Why do you need a view for this? Wouldn’t just a link and/or @DbLookup computed for display fields be more efficient?
Did you by any chance make a copy of the application and the application’s documents, that have different UNIDs than the values stored in the fields?
Create a toolbar button with the same formula as the single-category formula, plus it uses @Prompt to display the value. Is that a value that appears in the categorized view? (hint: no.) Copy the value to the clipboard, and open the view that’s categorized by unique ID, and use the client’s quick-search to search for that ID. Is it there?
Useful blog: Best Practice Makes Perfect
NOTE: My policy is to post only two responses to the same question. So that my second response can solve your problem rather than being a request for details, please read the C R I S P Y document.