Just found that I can't do it, and probably it is straight forward to solve it, though I don't know if it would be useful for others.
It might sound weird at first, since why one would want that?
It could be as simple as one might want to check side by side in an assembly how a part fits in two mirrored places using X-version and Y-version. Or for instance, if one has a linked model at an old version --with a lot of linked models, perhaps some out-of-date parts too, but you can't update'em all. If one drags another instance of the same model, it automatically gets the version of the old version in the assembly and not the latest.
I suppose this is not entirely bad, since some workarounds can be taken, but it'd be nice to choose versions indistintively, like if each linked model would be a branch or a fork from the original, and one could set that to point at different versions in history. Then if you implement something the edit-in-place like proposed here then it will act as a merge to the original history
If so, then the drop-down option of "Get Latest" should be split in "Get Latest for ALL instances" and "Get Latest for the CURRENT instance".
Thanks for such a great and complete tool, greetings from Barcelona, Spain.
Carlos
