Complex search not working

I am trying to execute a complex search of the following type and keep getting "parameter invalid". The logic of the search is like this:

(
(DOCNUM = 1 AND VERSION = 1)
OR
(DOCNUM = 2 AND VERSION = 1)
OR
(DOCNUM = 2 AND VERSION = 2)
)

I'm trying the following code to build my search query, what am I doing wrong?

IManOrQuery masterQuery = new ManOrQueryClass();
IManOrQuery q1 = masterQuery.AddOrQuery();
IManAndQuery andq1 = q1.AddAndQuery();
aq1.AddFieldQuery(imProfileAttributeID.imProfileDocNum).Values.Add("1");
aq1.AddFieldQuery(imProfileAttributeID.imProfileVersion).Values.Add("1");

IManAndQuery andq2 = q1.AddAndQuery();
aq2.AddFieldQuery(imProfileAttributeID.imProfileDocNum).Values.Add("2");
aq2.AddFieldQuery(imProfileAttributeID.imProfileVersion).Values.Add("1");

//dbList contains a manstrings object with my DB
session.WorkArea.SearchDocumentsEx(dbList, masterQuery);

Find more posts tagged with

Comments

jny

I am trying to execute a complex search of the following type and keep getting "parameter invalid". The logic of the search is like this:

(
(DOCNUM = 1 AND VERSION = 1)
OR
(DOCNUM = 2 AND VERSION = 1)
OR
(DOCNUM = 2 AND VERSION = 2)
)

I'm trying the following code to build my search query, what am I doing wrong?

IManOrQuery masterQuery = new ManOrQueryClass();
IManOrQuery q1 = masterQuery.AddOrQuery();
IManAndQuery andq1 = q1.AddAndQuery();
aq1.AddFieldQuery(imProfileAttributeID.imProfileDocNum).Values.Add("1");
aq1.AddFieldQuery(imProfileAttributeID.imProfileVersion).Values.Add("1");

IManAndQuery andq2 = q1.AddAndQuery();
aq2.AddFieldQuery(imProfileAttributeID.imProfileDocNum).Values.Add("2");
aq2.AddFieldQuery(imProfileAttributeID.imProfileVersion).Values.Add("1");

//dbList contains a manstrings object with my DB
session.WorkArea.SearchDocumentsEx(dbList, masterQuery);

What are you trying to ultimately achieve by your search, instead of how you're doing it?

Dave_Aronow

I am trying to search for specific documents based on complex criteria that will change. My sample was just an example of one of the basic searches I tried in an effort to figure out what my syntax error was.

jny

I am trying to search for specific documents based on complex criteria that will change. My sample was just an example of one of the basic searches I tried in an effort to figure out what my syntax error was.

I cannot get my arms around what you're ultimately trying to accomplish based on your example. If you could explain it with another example that is more practical, maybe I can help.

Also, there is a devnet article which has a bunch of examples on how to construct complex search queries. You may want to check it out to see if that'd help.

http://devnet.interwoven.com/site.fcgi/techlib/053221

guido1

I think what Dave is saying is that, given the code I included at the end of this message, you would expect the API to construct the following WHERE clause:
((DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 1)
OR
(DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 2)
OR
(DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 3))

Instead the API constructs the following:

((DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 1)
OR
(DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 2))
AND
(DOCMASTER.DOCNUM = 100 AND DOCMASTER.VERSION = 3)

Is this a bug? Or is there a valid API syntax which will construct this clause? The SDK and devnet articles don't include an example that fits the bill

I would expect every query added to a ManOrQuery entity to be OR'd.

var orQuery = new ManOrQuery();

var aq1 = orQuery.AddAndQuery();
var aq1DocNum = aq1.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
aq1DocNum.Values.Add("100");
var aq1Version = aq1.AddFieldQuery(imProfileAttributeID.imProfileVersion);
aq1Version.Values.Add("1");

var aq2 = orQuery.AddAndQuery();
var aq2DocNum = aq2.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
aq2DocNum.Values.Add("100");
var aq2Version = aq2.AddFieldQuery(imProfileAttributeID.imProfileVersion);
aq2Version.Values.Add("2");

var aq3 = orQuery.AddAndQuery();
var aq3DocNum = aq3.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
aq3DocNum.Values.Add("100");
var aq3Version = aq3.AddFieldQuery(imProfileAttributeID.imProfileVersion);
aq3Version.Values.Add("3");

Dave_Aronow

Yup, that's basically what I'm saying. Not sure why it matters exactly what I'm trying to accomplish, but here it goes.....

I have a list of "document/version candidates" from an external source (say a list of recent documents on the PC) and I want to make sure the user still has rights to view those documents by querying the API and finding which ones return from the query (assuming that if someone has removed the user's rights to a document it will not be returned from the complex query). I ended up doing this by retrieving each document separately, but I figured the complex query would let the API do the heavy lifting of "OR"ing the query (instead of me). So much for that.

While I'm asking, how come the 8.5 SDK documentation has last updated dates from 2007?

jny

Yup, that's basically what I'm saying. Not sure why it matters exactly what I'm trying to accomplish, but here it goes.....

I have a list of "document/version candidates" from an external source (say a list of recent documents on the PC) and I want to make sure the user still has rights to view those documents by querying the API and finding which ones return from the query (assuming that if someone has removed the user's rights to a document it will not be returned from the complex query). I ended up doing this by retrieving each document separately, but I figured the complex query would let the API do the heavy lifting of "OR"ing the query (instead of me). So much for that.

While I'm asking, how come the 8.5 SDK documentation has last updated dates from 2007?

Guido's search criteria example seems to demonstrate picking out versions of the same document number.

Your example targets different document numbers and their versions.

Going by Guido's example, if it's an Inclusive Or logic search, it will be similar to Example1 in the article as well as the code examples below.



//Inclusive Or Search Example

// Create ANDQuery
IManAndQuery andQuery = new ManAndQueryClass();

// Use AddFieldQuery to create an Or query (ex. DOCNUM="35094")
IManFieldQuery andQueryField = andQuery.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
andQueryField.Values.Add("35094");

// Use AddFieldQuery to build an Or subquery between values of the same attributeID
// (ex. VERSION="1" OR VERSION="2" OR VERSION="3")
IManFieldQuery oqC1 = andQuery.AddFieldQuery(imProfileAttributeID.imProfileVersion);
oqC1.Values.Add("1");
oqC1.Values.Add("2");
oqC1.Values.Add("3");

Another Inclusive Or search that returns more than one document is like so. Notice only the second field can be added with an AND field query to specify the return of a certain version. This is because the second one is a subquery to the first one. That is, you cannot form a complex query as: (DOCNUM=100 AND VERSION=1) OR (DOCNUM=102 AND VERSION=2). You can form it as: (DOCNUM=100) OR (DOCNUM=102 AND VERSION=2). You can also do: (DOCNUM=100) OR (DOCNUM=102 AND (VERSION=1 AND VERSION=2)). Basically, you can only add a single subquery after each field query; thus it becomes a subset of the last field query.


IManOrQuery orQuery = new ManOrQueryClass();

IManFieldQuery qDoc = orQuery.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
qDoc.Values.Add("35088");

IManAndQuery oqDoc = orQuery.AddAndQuery();
IManFieldQuery oqAndDoc = oqDoc.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
oqAndDoc.Values.Add("35094");
IManFieldQuery oqAndDocVer = oqDoc.AddFieldQuery(imProfileAttributeID.imProfileVersion);
oqAndDocVer.Values.Add("2");
oqAndDocVer.Values.Add("3");

You would need to repeat the search for a different doc number or a pair of numbers respective to the code examples above.

This example also demonstrates Inclusive Or for matching more than one document number to the specified version numbers:


IManAndQuery andQuery = new ManAndQueryClass();
IManFieldQuery oqVer = andQuery.AddFieldQuery(imProfileAttributeID.imProfileVersion);            
oqVer.Values.Add("2");
oqVer.Values.Add("3");

IManOrQuery oqDoc = andQuery.AddOrQuery();
IManFieldQuery oqAndDoc1 = oqDoc.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
oqAndDoc1.Values.Add("35094");
IManFieldQuery oqAndDoc2 = oqDoc.AddFieldQuery(imProfileAttributeID.imProfileDocNum);
oqAndDoc2.Values.Add("35088");

If, however, the attempt is to retrieve, say, either document 1_2 or document 2_2, but not both, then it looks like you'd like to do an Exclusive Or logic search, which I don't believe is supported.

I believe when there are newer interfaces to publish, the documentation will then be updated. I don't think there are newly published interfaces.

NewFile.xml