I’m showing users view data using ReadViewEntries to pull down the XML. They tag documents and those UNIDs get passed back to a server-side process using the “unid” attribute found in the XML. Works great.
I want them to be able to tag categories. No problem - there’s the “noteid” attribute in the XML too. From the Designer Help for the element:
noteid
%noteid;
#IMPLIED
noteid
NoteID of the document, if the view entry represents a document. If the entry represents a category, it is a category ID.
Nice! Well here’s the problem: There’s no corresponding backend property for matching up these “category IDs”. The NotesViewNavigator class has “noteid” and “unid” attributes, but they are always blank. There’s no reference to “category IDs” anywhere else in the Designer help, either.
Andre, if you read this, thanks again. I’m opening a PMR for this as well, but I’m hoping to possibly get an answer “from the horse’s mouth”. I’m hoping that there’s a way to get the category ID (I’m keeping my fingers crossed for an undocumented property).
Update: The PMR’s open-and-shut, with an SPR (#BMGN6W3TF7) made for the ehancement request. According to support there’s no property, undocumented or otherwise, that matches up to that attribute of the XML data – it just seems to be an oversight that it was nevere added. I’ll add it to my wishlist… the benefit to users of being able to process selected categories of documents on the backend would be huge.