Skip to main content
R
RS_1009568512-Amethyst
12-Amethyst
January 30, 2024
Solved

Issues with Classification Attribute

  • January 30, 2024
  • 1 reply
  • 3017 views

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.1

When setting up a binding attribute for partslink classification, if I leave the namespace and node fields blank in the classification constraint, I see the classification attribute in the create new part wizard, but there are no nodes to select. When I add the namespace value to my configured namespace, the classification attribute no longer appears in the new part wizard.

I see no errors in the MS logs

Best answer by RS_10095685

Ugh - false alarm.  It came down to licenses, despite using an org admin - still needs a PartsLink license!  Sometimes we overlook the simple things.  Thank you for the responses though!

1 reply

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
January 30, 2024

Can you share screen shots of your setup? I can compare to mine and then we can see where they are different.

R
RS_1009568512-AmethystAuthor
12-Amethyst
January 30, 2024

See photos below of Type/Attribute setup, Manage Classification window, and New WTPart Wizard.

 

Attribute Setup.JPGMechanical Node 1.JPGMechanical Node 2.JPGNamespace and Main Node.JPGNew WTPart Wizard.JPGPart Create Layout.JPG

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
January 30, 2024

In the constraint, the default namespace should be "com.ptc.csm.default_clf_namespace". Any reason you used "MyNameSpace"? I left my node field blank.

Terms & ConditionsCookie settingsAccessibility statement