MAJOR BUG : appenddoclink client 901(FP1) problem

A feature that always worked with the 8.5.3 client stopped working in the 9.0.1 client.

In database “A” there is a button on a form (read opened document) with lotusscript that creates a mail with a doclink (using appenddoclink) in the users mailfile and then the user can send this mail out.

In the 8.5.3 client :

  • Replica ID = db A

  • View ID = default view of db A

  • Note ID = the opened doc from db A

In the 9.0.1 client :

  • Replica ID = inbox user

  • View ID = default view of db A

  • Note ID = the opened doc from db A

The next error comes up (offcourse) "The linked document (UNID …) cannot be found in the view (UNID …)

One line of the code used to create the doc link

Call body1.appenddoclink(uidocdoc,“doclink”)

Subject: Provide sample

I’m not seeing any SPRs/APARs reporting similar issue. I tried but failed to reproduce what you’re seeing. Can you open up a PMR with IBM Support and provide a simple database that reproduces the issue so we can investigate.

Subject: QuickFix

I initially reported this problem in August’14. For the moment the only solution I found is to replace the code

Call NotesRichtTextItem.AppendDocLink( notesdocument , “Click here” )

with

Call NotesRichtTextItem.Appendtext( NotesDocument.NotesURL)

Hope this helps.

Regards

Daniel

Subject: It’s a known regression. We will fix it in a future fixpack

It regressed in 9.0. Sorry about that. There were 2 closely related doclink sprs. I’ll see if we can squeeze it into 901FP3 for January but may need to go to FP4

SPRID Description
Link Notes://CAMDB04/85256055004781F8/590174D9F2F2E370852579A50051D0D2/1FE087CC05AC630A85257BCF0002B316 RDJS9AT227 Lotusscript CopyToDatabase Overwrites ReplicaID Of Document Links To Destination Database
Link Notes://CAMDB04/85256055004781F8/590174D9F2F2E370852579A50051D0D2/6CBCC29C760A853F85257D80004B5408 XBXB9QCH55 Send a doc link created by AppendDocLink to another database,the link can be opened in Domino853,but failed in 901

Subject: New info - CopyToDatabase

Ok we narrowed the problem down to “CopyToDatabase”.

If we use this to copy a doc from one db to another the ReplicaID of the doclink gets changed.

Anyone with a solution?