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

Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X

Merging ProI Attribute Values

thomas_hogan_99
1-Visitor

Merging ProI Attribute Values

All,

I have2 attributes in Pro/I, Description* and Description. Don't know
how 2 were created, but they are there so I have to deal with them.

Most PIVs (>97%) have values in Description*. The remainder has values in
(Description) or (Description* and Description).

It would be a manual effort to figure out which Description value to
migrate. Fortunately it's pretty easy to determine the "right" value.

Is there a tool available to merge the attribute values in Pro/I into a
single Description* attribute?

Tom (thomas_hogan@verizon.net)

4 REPLIES 4

Description is the OOTB (built-in) attribute

Description* is a User Added attribute.



Why? Your guess is as good as mine.





--Jim Augeri

MCAD Tool Support - Engineering Quality and Tools (EQT)

Honeywell Aerospace

9201 San Mateo Blvd. (MS B-3)

Albuquerque, NM 87113

Phone - 505.828.5808

Fax - 505.828.5500

james.a.augeri@honeywell.com



This e-mail message and any attachments are for the use of the intended
recipient(s) and may be controlled by U.S. export control laws. Any
unauthorized review, use, disclosure or distribution of this
communication in whole or in part without the express written consent of
Honeywell, or the U.S. Government as required, is prohibited. If you are
not the intended recipient(s), please contact the sender by reply e-mail
and destroy the original message and any copies of the message as well
as any attachment(s) to the original message.


We have this too.

Is it possible that it comes from importing pre-existing data into
Intralink? In other words, if I had a Description parameter in Pro/E before
I installed intralink, then when I installed intralink, that got mapped into
Description* rather than Description.

Again, "Why? Your guess is as good as mine."







--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
Not applicable
(To:thomas_hogan_99)

Jim's correct.

"Description" (in the table configurator editor it shows with a pink dot) is a system attribute. This allows an object description to be entered for the object container (from a database perspective). This is a value that can be controlled and changed in ProI (and not in ProE).

"Description*" (shows with the user icon instead of the pink dot) is a ProE parameter that happens to have the same name that is only designated (shown) in ProI.

Naming is certainly confusing. When you throw in PTC_COMMON_NAME and epmdocument name and filename, it's get a bit worse (the CAD Data Admin 9.0 class has an excellent slide on this).

There are a couple of ways to look at solving the mapping for your migration. Feel free to contact me off-list for details.

Dan Harlan

I have been using Intralink since version 1.2



Back then there was no system attributes so naturally the one of first
attributes any system admin would create would be "Description"



A later revision then introduced predefined system attributes with one of
them being "Description", so we got stuck with both of them



Regards,

Robert Altman

CAD System Admin looking for a job.



_____
Announcements


Top Tags