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

We are happy to announce the new Windchill Customization board! Learn more.

Configuration of Windchill Quick Search

DareDevil
1-Newbie

Configuration of Windchill Quick Search

For some reason we do not pay much attention to the attribute PTC Common name in Creo/Windchill. But, when I do a quick search in Windchill this is one of the attributes that is searched upon. Now the question, can I change these preferences and for example make the search for filename instead? Is this possible?

1 ACCEPTED SOLUTION

Accepted Solutions

Do you have the index search running? Then you can define that this field is indexed as well

<Property name="wt.index.IndexFields" overridable="true"

targetFile="codebase/wt.properties"

value="name,lifeCycleState,description,number,title,containerReference,modifyTimestamp,filename"/>

If not, you will need to customize. But I would highly recommend that you rather think about the usage and cleanup of the NAME field. Usability will be so much better if you can use the name field for inline editing, etc and therefore you should think about a robust way to ensure good data. I agree that the solution does not a 100% job and you might want to implement some logic during the release process to ensure that the name field is in synch with the "COMMON_NAME" or any other attribut you feel is appropriate. For the data already in the system you should fix this by some scripts.

View solution in original post

6 REPLIES 6

Cannot search directly for filenames in today's Windchill.

Think of it more as searching for a container (the CAD Document), which has as it's primary identifier the (unique) NUMBER, and also a NAME. These are on the container; the container holds a Primary content File, and possibly one or more Attachment or Secondary content files.

But what about the indexing for the content? Is that just my wishful thinking?

just go to advanced search and add new criteria, in the more section you will find filename. Save this search for later reuse and publish to other users if required. Windchill can do almost everything but not always obvious.

Hi, sorry if I was unclear. I know how to do a pre defined saved search. Then I have to go to the advanced search page and get to this "complicated" UI. I what to choose the way that Windchill carry out the Quick Search.

Do you have the index search running? Then you can define that this field is indexed as well

<Property name="wt.index.IndexFields" overridable="true"

targetFile="codebase/wt.properties"

value="name,lifeCycleState,description,number,title,containerReference,modifyTimestamp,filename"/>

If not, you will need to customize. But I would highly recommend that you rather think about the usage and cleanup of the NAME field. Usability will be so much better if you can use the name field for inline editing, etc and therefore you should think about a robust way to ensure good data. I agree that the solution does not a 100% job and you might want to implement some logic during the release process to ensure that the name field is in synch with the "COMMON_NAME" or any other attribut you feel is appropriate. For the data already in the system you should fix this by some scripts.

Oliver Droop ha scritto:

Do you have the index search running? Then you can define that this field is indexed as well

<Property name="wt.index.IndexFields" overridable="true"

targetFile="codebase/wt.properties"

value="name,lifeCycleState,description,number,title,containerReference,modifyTimestamp,filename"/>

Hello,
I take this old thread to ask if the proposed solution can also be valid in Windchill 10.1, also if it is possible to make the same change, research on filename, even when you make a save as option with Replace.

Thank you

Ps.
Sorry for the translation of google

Top Tags