Family Table Corruption from Intralink

[Richard_Thell]

Help!


Have a relation driven parameter to discribe the hardware the user is selecting from a family table of metric plain washers.


desc_line1=pre_fix+nominal_size+washer_series
pre_fix='PLAIN WSHR, '


desc_line1 is the "designated" description parameter in intralink.


pre_fix is the start of the description followed by string parameters from the family table.


The result is a relation locked description for each instance.


Similar relations have worked well for other fam tab hardware I've created


for some #$@!% reason when the generic is checked in the library (only L has write privilages) then the same rev and version number is checked out.


the nominal_size (1.6 mm, for example)String is replaced by 4.000000000010


odd and larger and larger numbers (5.0000000010 ... 110.00000000000056)


The washer_series (NARROW for example) string is not affected


Now the poor user has no idea what the part is when trying to select the instance by parameter.


ptc mechanical support says relation string is fine must be intralink call them


ptc Intranlink support says intralink is fine must be the relation.

 

[charleskim]

Is your problem where correct description is not showing up in Intralink?


I assume you have "desc_line1" designated.


Do you have "desc_line1" in family table?


You need to have"desc_line1" in family table (as driven by relation) for it to show correct description in Intralink.


I hope this is what you are after.


Charles

 

[Richard_Thell]

Thanks for responding so quickly Charles,


The "designated" description or "desc_line1" is populated in intralink properly upon check in.


desc_line1 is in one of the generic parameters but is NOT in the family table.


pre_fix+nominal_size+washer_series are in the family table.


I'm using the relation to group the parameter strings together to give each instance an individual description. I have used this technique successfully on other hardware without "disc_line1" in their tables.


The beauty is I do not have to create a description for each instance. Verification does that for me.


My last resort is to remove the relation and add "desc_line1" as a column and manually add each description to each instance 100 times.

Intralink should not be replacing the string value of "nominal_size". Though I could bemaking a bad assumptionand I've just been lucky up until now.


Any feedback is welcome.


Regards,


Richard

 

[charleskim]

I think you are on the right track.


I'm assuming that 'desc_line1' is parameter you are using in Intralink.


What is happening is, Intralink is not replacing with "nominal_size", instead Intralink doesn't know about values of instances because it is not in family table.


In your relation file, add (if you don't have it already)
desc_line1 = pre_fix+nominal_size+washer_series


Then add 'desc_line1' in family table and run verify, this should fill it out automatically with (same information as pre_fix+nominal_size+washer_series) and this will be driven by relation.


Good luck Richard

 

[looslib]

Waht version of Intralink are you using?


In 3.x it handles the description fields a lot diffferently than 8.0. I ran into several problems with attribute description strings when we migrated from 3.3 to PDMLink 7.0.

 

[Richard_Thell]

Hello Loos


We are using 3.3 and eventually planning to jump straight to windchill or plm on demand. The problem with using"description" as a parameter is that it is a system defined attribute that can only be changed when submitted into common space. If we create a duplicate user defined attribute it puts a * in front of the name IE. *description. a parameter with a * in front of it can cause all kinds of issues. So desc_line1 was born.


Regards,


R