cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Searching with Multiple Criteria using AND statement?

ocorten-2
8-Gravel

Searching with Multiple Criteria using AND statement?

Is there a way to change the behaviour for multiple Search Criteria in Windchill?

Currently multiple criteria are treated with an OR statement (even though With All of These Criteria is set)
But I would like to use multiple criteria with an AND statment.

e.g. Search forFile Name equals 1003* or 1005*
ANDFile Name does not equal *xx* or *yy*
The search below in WC gives an error (search result size has exceeded the limit) because it treats both criteria with an OR statement and thus yield too many results with the second criteria:




(... we are on Windchill Intralink 9.1 M050)


Kind regards,

Olaf Corten





Olaf Corten
CAD/PLM Manager
Fico B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com

*** nov. 10th - PTC/USER Benelux Event 2010 -
9 REPLIES 9

Olaf,

Add the following property to the wt.properties file:
com.ptc.windchill.search.client.overrideAndOrOperator=true
Dominic Hand
PLM Deployment & Support Leader
Climate Solutions
Ingersoll Rand
314 West 90th Street
Minneapolis, MN 55420


Office +1.952.887.2247
Mobile +1.612.384.4366
Fax +1.866.806.9284

Great discussion, just to clarify, docs say this:

The Search Criteria table allows you to build detailed search queries by
selecting specific searchable attributes and specifying the attribute
values on which to search.

Note: Multiple values can be specified for attributes by adding the
attribute to the table more than once. If you specify multiple values
for a single attribute, there is an implicit OR relationship between the
two values. For example, if you specify the Name attribute twice, with
values of part* and gear*, your search returns results which match
either of those values.



So, this wt.property setting switches it to an implicit AND
relationship?



Olaf, where did you pick up the convention of delimiting multiple search
criteria with a semicolon? I could not find that documented. This allows
you to do ANDs and Ors now. Great work.


Antonio,

Yes, that is correct. The property below changes the advanced search behavior such that it treats multiple criteria for the same attribute with an AND relationship instead of the default OR relationship. This has been tested and implemented successfully in PDMLink 9.1 M040.

com.ptc.windchill.search.client.overrideAndOrOperator=true

Dominic Hand
PLM Deployment & Support Leader
Climate Solutions
Ingersoll Rand
314 West 90th Street
Minneapolis, MN 55420


Office +1.952.887.2247
Mobile +1.612.384.4366
Fax +1.866.806.9284

Great man, just what I was looking for. Will try it asap.

The semicolon was discovered by one of our users who just copied the Intralink 3,.4 functionality and tried in 9.1.
BTW, The semicolon does not work in the Keyword field unfortunately. So the search below returns nothing:


Kind regards,

Olaf Corten





Olaf Corten
CAD/PLM Manager
Fico B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com

*** nov. 10th - PTC/USER Benelux Event 2010 -
To: "Villanueva, Antonio" <->, Olaf Corten <->, "-" <->
Date: 14-10-2010 16:40
Subject: [solutions] ...



















saw
10-Marble
10-Marble
(To:ocorten-2)

I have noticed that this search is much slower than a single criteria name or number search.

Stephen Worthington

mlockwood
19-Tanzanite
(To:ocorten-2)

May be related to wildcards. Seems to be immediate for a long list if the entire Number is included.
saw
10-Marble
10-Marble
(To:ocorten-2)

I have used a full file name including extension just to try my theory and it still seems slow.

Stephen Worthington

Name and number input fields searches only mastered objects I believe, where the regular keyword field when a name or number is used searches more objects regardless if fast search is installed or not. I guess PTC could chime in on that angle.



Sent from my Verizon Wireless BlackBerry

Olaf great thread



May I point out that there is a better way to solve some of these issues.

Many companies today force their end users to use metadata in the parts and
assemblies in hopes of

being able to search on many areas so they can find the necessary
information at a later date,

The problem lies within the fact that many things cannot be processed into
canned fields

and as such are prone to human interaction and ways of thinking, not to
mention international companies

such as on these forums where a boot in Texas and a boot in Europe are
completely different items.



We recently showed a large international company their own database of
parts, we asked them for any part

name and showed them the results based upon that part name, we then did a 3D
geometry search on

that part and found 5X the number of parts due to simple syntax differences.
( and many duplicates )



We don't take away the option to search on text/metadata we simply enhance
the search criteria

and chances for success by bringing in the aspect of a search engine that is
100% accurate based on shape of 3D part.



We have had a booth at PTC world for the last 3 years



This is installed at some very prominent companies utilizing many different
PDM systems.



If you are interested take a glance at the website and video



if you want to continue to struggle with identifying parts and
assemblies based upon textual fields . then delete this email



Thanks

Kelly 713-784-3500



www.3dcadseek.com
Announcements