DeleteRendition issue

[ahaboub]

Hello,
I am using the LAPI DeleteRendition function to delete document's rendition, the renditions are being correctly deleted (there is no more any rendition files in the rendition tag for the document version)
but the issue is that the renditions are still appearing in the search result. do i need to synchronize the search? or is there any operation i missed?

thanks and regards

 

[appnair]

when you delete anything in livelink that gets queued into the dtreenotify table and that is all you have to do the livelink search engine will take care of the rest.Make sure your lapi call is completely purging it which you can verify by running the search and trying to open a rendition.if the open action fails then the livelink database has no record of the object.if it works then you have not completely removed everything.In either case if you feel this is not working according to spec then Ot support has to be involved.
Resynchronizing is the process of taking what is contained in the livelink database and writing config files for livelink.It does not cause any re-indexing .

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[ahaboub]

Thanks for your answer appnair.

In fact, in the search result i can see the document (size 18k) and its rendition (size 0k), i go to the location and check the document properties, there is no rendition!! i even checked the properties of the version, there is no rendition also.

i will try to open the rendition and see what will happen...

does a re-indexing solve the issue?

 

[appnair]

re-indexing means that you will put everything in your dtree again for requeuing which cannot be used in a productive livelink all the time.if your lapi call is doing its job as advertised then you need to make it known to OT.I would just try to be devil's advocate and create a rendition for a known version(note its dataid).Then with the extractor stopped in admin server look in the table dtreenotify.If you see the nodeid coming there then you know that the addrendition stuff has added it for the search indexer.Then I will run the extractor until the rows vanish.Similarly using the GUI i would delete the rendition and observer dtreenotify.Repeat with your lapi call.If the GUI call is successfully telling the indexer a delete has ocurred on a dataid and your lapi call is not doing it it probably is something wrong with lapi or your program.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[ahaboub]

the code is doing the same as the manual process you suggested: i have the node in the dtreenotify, and later it vanishes...

if it matters, i am simply using the following function:

status = lDoc.DeleteRendition(0, docID, 0, tbo_RenditionName.Text)

 

[appnair]

so you may have to see if the deleterendition in the GUI actually does remove it from the searchindex if not then it could be a bug although I would hesitate to approach OT if you have put requires patches et al for your system.
the basic premise is when anything on a node(create,update,delete,rename) happens on a node the livelink code puts it in dtreenotify for telling the searchindexer what to do with it.it may not be immediate but usually when the node completes the indexing cycle it should be removed /added etc from the search index.I cannot tell you one way or the other if all your search processes are working or not.So please repeat or contact ot after you have done your homework.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[ahaboub]

ok, thanks appnair

 

[appnair]

also OT allows you to 'insert into dtreenotify' for manual re-indexing one of the few tables that can be manipulated without fear of callback problems in livelink.The exact syntax for doing such an action is usually given out by ot support or it can be found in the Knowledge Base.when ipool corruption occurs that is the only way to get those nodes again indexed...

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair