Windchill Needs A Default Value to Add an Attribute to a Class - Partslink

[sdrzewiczewski]

Is there a way to add attributes without having a default value? I tried using the AllClients.xml file to not display the default value, but it didn't appear to work for classification attributes.

I may be missing something, but it seems like it should require a default value.

TIA

Steve D.

[AL_ANDERSON]

We use PDMLink 9.1 and for String IBA with a discrete set (drop down box)
of values, we could not make the default be blank.

What we really want and need is the ability to have a drop down box
default to blank on create, but be a mandatory field - forcing the user to
purposely enter a value, rather than leaving the non-blank default.

What we ended up doing, even though we don't like it, is using values like
'-' or "BLANK" as the default, as shown below, to indicated that the value
has not yet been selected.

Here is an example of 3 IBA default values on a WTPart light type, showing
'-' as the default.



Here is an example of using "BLANK" as the default value in one of our
classifiation IBAs for a "Bearing Lockwasher."



We found this to be acceptable. But we really need blank as default, and
the ability to force a selection on creation rather than using '-' or
"BLANK."

Al Anderson
Solar Turbines Incorporated






Stephen Drzewiczewski <->
07/27/2011 11:58 AM
Please respond to
Stephen Drzewiczewski <->


To
-
cc

Subject
[solutions] - Windchill Needs A Default Value to Add an Attribute to a
Class - Partslink




Caterpillar: Confidential Green Retain Until: 08/26/2011



Is there a way to add attributes without having a default value? I tried
using the AllClients.xml file to not display the default value, but it
didn't appear to work for classification attributes.
I may be missing something, but it seems like it should require a default
value.
TIA
Steve D.

Site Links: View post online View mailing list online Send new post
via email Unsubscribe from this mailing list Manage your subscription
Use of this email content is governed by the terms of service at:

[sdrzewiczewski]

Do you have any attributes that are not discrete set constraints?



We have some attributes that are strings without lists. I could put in a
- or BLANK for those, don't love it, but could live with that.



We also have several attributes that are Real Number with Units. I don't
want to default something like 0 in as the default value.



Do you have similar issues?



Thanks,

Steve D.

[sdrzewiczewski]

I have figured out the solution. The answer is what I thought it was, to
use the AllClients.xml file located in
Windchill\codebase\config\logicrepository\xml\AllClients.xml



The problem I was having is when you set the entries you need to use the
Name of the attribute not the LogicalID. So for any one word attributes
it was working correctly, any multiword attributes it wasn't because
LogicalID can't contain spaces and Name can. Attached is a sample file
that shows the format to blank out the Default Values on the create
form.

[sdrzewiczewski]

We are in the process of upgrading to 10.1 and the AllClients.xml file is no longer supported. I have not found a way to remove the need for default values on Classification attributes or the display of default values on Classification attributes.