.NET LAPI Search problem

I have the following code in C# .Net, the query seemingly runs ok without errors, but returns no results. I have checked that I am using the correct search broker and project id to search under. If I run a search with the same criteria in LL I get lots of results:string whereStr = "( \"OTLocation\" : \"" + dataID + "\" ) AND ( \"OTName\" : \"test\" )";searchResults = (new LLValue()).setAssocNotSet();LLValue selectList = (new LLValue()).setList();selectList.add("OTName");selectList.add("OTObjectDate");if(search.ApplyQuery(searchBroker,selectList,whereStr,LAPI_SEARCH.SORTBYDEFAULT,"",1, 10, "LivelinkQueryLanguage", searchResults) == 0) { int length = searchResults.size(); outPut += "
Items found: " + length + "
"; outPut += ""; outPut += "NameDate"; for(int i = 0; i < length; i++) { outPut += ""; } outPut += "

" + searchResults.toValue(i)).toString("OTName") + "

" +(searchResults.toValue(i)).toString("OTObjectDate") + "

";} else { outPut += "
Query Failed."; GetErrors();}

Find more posts tagged with

Comments

Mahim_Sharma_(mahimsharma_-_(deleted))

Hi Mat,Your code looks perfect except the value for searchBroker.You need to get the dataid of any one of the available Livelink Search Brokers.I hope u will be having better ideas about search brokers.Get the searchbrokerid by calling GetSearchBrokers(LLValue llval).Hope this helps u .

Nicolas_Gingras

I was also in the process of using the LAPI search methods and I got the exact same problem as you. Again, this seems to be either a lack of documentation problem or a bug. I looked at the OScript that runs when executing the query and deep somewhere, it validates if OTObject has a length BUT, the OScript part of the LAPI search doesn't append it automatically (as I think it should do if this is a requirement and that's why I think it's a bug) so if you want to get results, add selectList.add("OTObject");

Nicolas_Gingras

Louis

Nicolas_Gingras

The forHowMany parameter seems to also be a bit buggy: you request 20 you get 21, you request 5 you get 6.So, another "0-based" value! :PSubstract 1 until the bug is corrected (in fact, could they correct it as it would make existing applications crash :S)

eLink User

Message from Carsten Kulms via eLink> this seems to be either a lack of documentation problem or a bugThis requirement is noted in the documentation of applyQuery method:----8<--------8<--------8<--------8<----Input Parameters[...]selectList an LLVALUE of type List containing string elements specifyingthe names of the fields to be retrieved from the searchable object;field names are case-sensitive and must be specified exactly as theyappear in the object. Note: You must specify the OTObject region inorder to satisfy Livelink's data retrieval and validation code. ----8=--------8=--------8=--------8=----[(LES 9.5) Livelink API Developer's Reference Guide: Search API]However, I agree it would be an improvement if "OTObject" wasautomatically added to selectList.

Nicolas_Gingras

Shame on me :SI probably was a bit quick on this one. As they often say: RTFM.