@command(OpenDocument] by unid sometimes opens wrong doc

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: @command(OpenDocument] by unid sometimes opens wrong doc

Feedback Type: Question

Product Area: Notes Client

Technical Area: Application Development

Platform: Windows

Release: 8.5.3

Reproducible: Always

I have a Notes client app that uses doc/response doc hierarchy.
I have @Function code in the response doc that saves/closes the response doc, opens the parent in the UI, updates a couple of fields, then saves and closes the parent. There's code in the parent's querySave that updates all response docs hence the need to open the parent in the UI and execute a save.

Most of the time, this works fine; I can see the parent open, all fields update as expected, and the response docs get the new values.

I'm finding a few instances where the system doesn't open anything, keeps focus on the closed response doc, update it, and acts like everything is fine.

I've confirmed I'm properly setting the UNID used by the OpenDocument command.

I can't find any references that say there are cases where opening a doc via UNID will not work. Any ideas?

Now for the specifics.
If I open the parent and set the fields that are updated by the child to random values, save/close the parent, and then update the child, I have the problem.
If I do an all view refresh <ctrl><f9> immediately after manually editing the parent, I'm not seeing the problem.
There's nothing in any of the code that modifies the parent UNID.

Why would view indexes affect @Command([OpenDocument]...)?

Thanks for any suggestions.

Feedback number WEBB9T7JT4 created by ~Martha Lopjipyskioden on 01/28/2015

Status: Open
Comments: