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

Warning - Designated dimensions, Intralink vs PDMLink

ejhlti
1-Newbie

Warning - Designated dimensions, Intralink vs PDMLink

I originally posted this message on the Windchill forum, but for those considering the move from Intralink to PDMlink, you may want to take a look at this.

Here is an issue were now faced with using PDMlink (9.0 - M050). As an example, a user creates a proe model. Rather than use the default proe dimensions (d1, d2, d3 etc), they rename the dimensions to more recognizable names like length, width and height. These renamed dimensions are also designated in proe. In Intralink 3.x, if you had corresponding Intralink parameters length, width and height, the proe dimensions would be passed to the Intralink database, so when you look in Intralink you can see these dimensions. Well looks like the rules have changed with PDMlink, it no longer likes to deal with renamed proe dimensions. Using the same example (attributes length, width and height exist in PDMlink), if a user has a proe model with renamed dimensions, the parameters wont get passed from Proe to PDMlink. When the proe prt is saved, the attributes disappear altogether in pdmlink. When saving in pdmlink, event manager gives warning that dimensions d1, d2, d3 are not pdmlink attributes. Keep in mind the proe model no longer has dimensions d1, d2, d3 etc, they were renamed length, width and height. So far only solution is to rename all proe dimensions back to original name and set relations like length=d1 etc. Has anyone else out there come across this issue ? Moving forward its one issue to change this, but to have to go back and modify every existing file to work this way is hardly an answer. Once again this is a prime example of how PTC will just change functionality with no regards as to what consequeces long time customers may experience. For anyone out there consdiering a migration, this is certainly something to think about.

0 REPLIES 0
Announcements


Top Tags