topic Re: Advanced Search Attributes in Windchill Customization

Advanced Search Attributes

Turko — Mon, 26 Jan 2026 17:58:24 GMT

Version: Windchill 13.0

Use Case: I am trying to setup an "Advanced Search" against the "Change Notice" object type. However, I have noticed I have no option to add any "Attributes" into the "Criteria" section of my search. Please refer to the attached image.

Description:

I have noticed that I can select other object types which provides the opportunity to add attributes into "Criteria" section of the search. Can anybody suggest why I don't have this option for the "Change Notice" object type?

Re: Advanced Search Attributes

TDT — Tue, 27 Jan 2026 02:08:44 GMT

Hi @Turko,

It works fine on my system.

I just wanted to check whether any attributes are displayed when you click on Add Condition?

Re: Advanced Search Attributes

Turko — Tue, 27 Jan 2026 10:20:51 GMT

Hello @TDT

Nothing seems to happen at all when I select "Add Condition"

Re: Advanced Search Attributes

TDT — Tue, 27 Jan 2026 10:26:35 GMT

Anything in Method Server logs?

Re: Advanced Search Attributes

Turko — Tue, 27 Jan 2026 11:05:35 GMT

Not sure if these are related to the issue but these crept up at a similar time that I tried to select the "Add Condition" button:

2026-01-27 10:54:12,164 ERROR [QueryBuilder Type Pre-Loader] com.ptc.core.lwc.common.view.AttributeDefinitionReadView - Invalid mapping : theChangeable2@wt.change2.RelevantRequestData2~theChangeRequest2^xxx_ChgMgmtReview~state.state for attribute : alias_state ATI : WCTYPE|wt.doc.WTDocument|xxx_DesignChgDoc com.ptc.core.meta.common.impl.LogicalAttributeFormatException: Unable to find logical attribute: "xxx_ChgMgmtReview"
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:770)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:504)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory.get(LogicalIdentifierFactory.java:300)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:576)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:504)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory.get(LogicalIdentifierFactory.java:339)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:548)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:549)
at com.ptc.core.meta.common.impl.LogicalIdentifierFactory.get(LogicalIdentifierFactory.java:1088)
at com.ptc.core.lwc.common.view.AttributeDefinitionReadView.initAttributeTypeIdentifier(AttributeDefinitionReadView.java:973)
at com.ptc.core.lwc.common.view.AttributeDefinitionReadView.getAttributeTypeIdentifier(AttributeDefinitionReadView.java:858)
at com.ptc.core.lwc.common.view.AttributeDefinitionReadView.getAttributeTypeIdentifier(AttributeDefinitionReadView.java:1952)
at com.ptc.core.lwc.server.cache.ConstraintFactory.getConstraintDefViews(ConstraintFactory.java:224)
at com.ptc.core.lwc.server.cache.ConstraintHelper.translateUnpersistedConstraints(ConstraintHelper.java:696)
at com.ptc.core.lwc.server.cache.ConstraintHelper.translateAttConstraintsToViews(ConstraintHelper.java:652)
at com.ptc.core.lwc.server.cache.AttHelper.translateAttDefsToViews(AttHelper.java:1120)
at com.ptc.core.lwc.server.cache.TypeDefinitionManager.translateTypeDefToView(TypeDefinitionManager.java:2874)
at com.ptc.core.lwc.server.cache.TypeDefinitionManager.retrieveAndCacheType(TypeDefinitionManager.java:625)
at com.ptc.core.lwc.server.cache.TypeDefinitionManager.getTypeDefView(TypeDefinitionManager.java:802)
at com.ptc.core.lwc.server.StandardTypeDefinitionService.getTypeDefView(StandardTypeDefinitionService.java:486)
at com.ptc.core.lwc.server.StandardTypeDefinitionService.getTypeDefView(StandardTypeDefinitionService.java:1056)
at jdk.internal.reflect.GeneratedMethodAccessor222.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
at jdk.proxy2/jdk.proxy2.$Proxy37.getTypeDefView(Unknown Source)
at com.ptc.core.lwc.server.LWCLocalizedValuesAugmentor.augment(LWCLocalizedValuesAugmentor.java:176)
at com.ptc.core.meta.descriptor.server.impl.AbstractLocalizedValuesFactory.addToLocalizedValues(AbstractLocalizedValuesFactory.java:678)
at com.ptc.core.meta.descriptor.server.impl.AbstractLocalizedValuesFactory.get(AbstractLocalizedValuesFactory.java:165)
at com.ptc.core.meta.descriptor.common.impl.RetrieveDefinitionDescriptorRemoteWorker.doWork(RetrieveDefinitionDescriptorRemoteWorker.java:62)
at com.ptc.core.command.common.RemoteWorkerHandlerImplementation.handleRemoteWorker(RemoteWorkerHandlerImplementation.java:29)
at com.ptc.core.meta.common.RemoteWorkerHandler.handleRemoteWorker(RemoteWorkerHandler.java:38)
at com.ptc.core.meta.descriptor.common.impl.DefaultDescriptorFactory.get(DefaultDescriptorFactory.java:184)
at com.ptc.core.meta.descriptor.common.impl.DefaultDescriptorFactory.get(DefaultDescriptorFactory.java:225)
at com.ptc.core.query.report.command.server.ReportTypeModelCommandDelegate.doExecution(ReportTypeModelCommandDelegate.java:155)
at com.ptc.core.command.common.delegate.AbstractCommandDelegate.execute(AbstractCommandDelegate.java:216)
at com.ptc.core.command.common.CommandDelegateForwarder._remoteExecute(CommandDelegateForwarder.java:284)
at com.ptc.core.command.common.CommandDelegateForwarder.remoteExecute(CommandDelegateForwarder.java:232)
at com.ptc.core.command.common.CommandDelegateForwarder.execute(CommandDelegateForwarder.java:194)
at com.ptc.core.command.common.bean.AbstractServerCommand.execute(AbstractServerCommand.java:202)
at com.ptc.core.query.report.common.impl.TypeDisplayInfo.buildTypes(TypeDisplayInfo.java:159)
at com.ptc.core.query.report.common.impl.TypeDisplayInfo.<init>(TypeDisplayInfo.java:109)
at com.ptc.core.query.report.common.impl.TypeDisplayInfo.<init>(TypeDisplayInfo.java:115)
at com.ptc.core.query.report.common.impl.TypeDisplayInfo.getTypes(TypeDisplayInfo.java:76)
at com.ptc.windchill.enterprise.queryBuilder.StandardQueryBuilderService$TypePreLoader.run(StandardQueryBuilderService.java:173)
at java.base/java.lang.Thread.run(Thread.java:833)

2026-01-27 10:56:18,267 ERROR [wt.intersvrcom.SiteMonitor.timer] wt.intersvrcom.SiteMonitor - Names=[xxxxxx], URL=xxxWindchill/servlet/WindchillGW, Status=SERVLET ENGINE NOT RESPONDING, ResponseSeconds=0.965, TimeOfPing=2026-01-27 10:56:16.401 +0000

Re: Advanced Search Attributes

TDT — Tue, 27 Jan 2026 12:46:27 GMT

Hi @Turko,

There appears to be an invalid alias attribute mapping.

Please refer to the following article to resolve this issue.

https://www.ptc.com/en/support/article/CS429528?source=search

Re: Advanced Search Attributes

Turko — Tue, 27 Jan 2026 20:31:19 GMT

Thanks @TDT but I don't think this is likely to explain why I have no attributes available to add to my criteria for an "Advanced Search" and cannot activate the "Add Condition" functionality. Would you agree?

Re: Advanced Search Attributes

TDT — Wed, 28 Jan 2026 02:58:14 GMT

Ok, Have you tried addressing the Alias Mapping issue to see if it resolves the problem?

Re: Advanced Search Attributes

Turko — Wed, 28 Jan 2026 07:44:47 GMT

I have not yet no. This is what I was referring to in my last post. I wasn't sure if it was related to the issue. However, if you fell it could be, I will prioritize looking into this.

Re: Advanced Search Attributes

TDT — Wed, 28 Jan 2026 08:34:57 GMT

Hi @Turko,

I was able to reproduce the issue to some extent.

I encountered the same error on my system.

2026-01-28 09:28:43,942 ERROR [ajp-nio-127.0.0.1-8010-exec-4] com.ptc.core.lwc.server.cache.AttValidatorHelper pdmadmin - Invalid mapping value: ~theChangeRequest2^xxx_ChgMgmtReview~state.state com.ptc.core.meta.common.impl.LogicalAttributeFormatException: Unable to find logical attribute: "xxx_ChgMgmtReview"

at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:770)

at com.ptc.core.meta.common.impl.LogicalIdentifierFactory._translate(LogicalIdentifierFactory.java:504)

Steps to reproduce

I attempted to add the alias attribute created on the Change Notice to Advanced Search using the following command
xconfmanager --add advancedSearch.wt.change2.WTChangeOrder2=testAlias -p

After executing this command, the other attributes are no longer visible.

Re: Advanced Search Attributes

Turko — Mon, 02 Feb 2026 17:48:24 GMT

Yep! This certainly only started happening after I attempted to add some custom attributes to the list of available attributes to select from in the "Criteria" section of advanced search.

Any idea how this command can be used without removing all of the attributes that were available there previously? Or how the previous attributes can be restored?

Re: Advanced Search Attributes

TDT — Wed, 04 Feb 2026 04:38:07 GMT

Hi @Turko,

You need to remove the alias attribute added to the advanced search.

I have just confirmed with PTC that alias attributes cannot be added to Advanced Search.

Re: Advanced Search Attributes

Turko — Fri, 06 Feb 2026 06:59:51 GMT

Thank you so much for your support @TDT , have a good day.

Re: Advanced Search Attributes

Turko — Tue, 10 Feb 2026 08:54:48 GMT

Good morning. I've been looking into this and I cannot see that the alias attribute is included in either my "projectmanagement.SearchableAttributesByType.properties.xconf" or the "SearchableAttributesByType.properties.xconf" file, both referenced in https://www.ptc.com/en/support/article/CS180432?source=search.. I think these are the only files I would have directly modified to try to add my attributes into the advanced search criteria. After modifying these files, I would have ran the "xconfmanager -p" command.

I have looked at these two files today and they don't appear to include any alias attributes. I have ran the "xconfmanager -p" command again after establishing this but my issue still exists.

I'm assuming that the issue exists because the "xconfmanager -p" command has propagated the original changes I made to the two .xconf files to include the alias attribute/s into other files. If this is the case, I will need to identify which files have been updated as a result of running the command originally and try to fix these.

Does this seem likely?

Re: Advanced Search Attributes

TDT — Tue, 10 Feb 2026 10:25:37 GMT

Hi @Turko,

Could you please check your site.xconf file once?

Re: Advanced Search Attributes

Turko — Tue, 10 Feb 2026 11:56:57 GMT

Sure. What am I looking for exactly?

Re: Advanced Search Attributes

TDT — Tue, 10 Feb 2026 14:09:03 GMT

As you mentioned that you cannot see the Alias Attribute listed in either the projectmanagement.SearchableAttributesByType.properties.xconf file or the SearchableAttributesByType.properties.xconf file, there is a possibility that the property was added in site.xconf.

Alternatively, you can search for the internal name of the Alias Attribute across the entire Windchill directory, filtering only for .xconf files.

You may use tools such as Agent Ransack or Notepad++, either of which should be sufficient for this purpose.

Re: Advanced Search Attributes

Turko — Tue, 10 Feb 2026 17:51:53 GMT

So to confirm, the "alias_state" attribute does not feature in the "Site.xconf", "projectmanagement.SearchableAttributesByType.properties.xconf" or "SearchableAttributesByType.properties.xconf" file.

I am doubtful that this alias attribute has anything to do with the issue I am encountering though. The attribute should not be associated with the object type I am unable to add attributes against within the "Advanced Search" tool. So, I don't see how the error message I am seeing in the log files to do with this alias attribute could be impacting my issue detailed in this post?