Better Control the Data format database attribute sync from TcEng to NX

Posted on Mar 7th, 2008 | 5010 commentshttp%3A%2F%2Fplmexchange.net%2Fbetter-control-the-data-format-database-attribute-sync-from-tceng-to-nx%2FBetter+Control+the+Data+format+database+attribute+sync+from+TcEng+to+NX2008-03-07+22%3A58%3A42adminhttp%3A%2F%2Fplmexchange.net%2Fbetter-control-the-data-format-database-attribute-sync-from-tceng-to-nx%2F

Starting in Teamcenter Engineering 2005 SR1 MP3, they have added a new format string. In the “IMAN_BASE_DIR\lang\textserver\en” is a file for time. Add the following key:
<key id=”NXDefaultDateFormat”>%d-%b-%Y</key>  

Restart your Teamcenter Service and open your drawings now it will have the DDMMYYYY format. If you want other formats there are other variables to get different results.

Site Standards (Load Latest)

Posted on Feb 25th, 2008 | 4994 commentshttp%3A%2F%2Fplmexchange.net%2Fsite-standards-load-latest%2FSite+Standards+%28Load+Latest%292008-02-26+01%3A43%3A37adminhttp%3A%2F%2Fplmexchange.net%2Fsite-standards-load-latest%2F

Customer defaults has a site standards section under assemblies section.

You need to define your naming convention using regular expressions. In your case you have 6 digit part number with an ‘underscore’ two digit number.

An example Regular expression for your site standards would be: (each line represents each section in the site standards)
([0-9]{6})(|_[0-9]{2})
\1
\1(|_[0-9]{2})
\2

Set the rule to numeric.

Another example would be:
([dD]?[0-9]{2}[a-zA-Z]?[0-9]{5,7})(|([a-zA-Z]{1,2}))

which would be for parts in this type of series:
1234567
12345678
123456789
d1234567
d12345678
d123456789

1234567_a
12345678_a
123456789_a
d1234567_a
d12345678_a
d123456789_a

Set your load options to load latest (now available since you set your site standards).

NX/Manager

Posted on Jan 10th, 2008 | 4972 commentshttp%3A%2F%2Fplmexchange.net%2Fnxmanager%2FNX%2FManager2008-01-10+14%3A42%3A48adminhttp%3A%2F%2Fplmexchange.net%2Fnxmanager%2F

When you do a saveas from NX into Teamcenter Engineering, a Teamcenter variable comes into play. This is:

DATASET_saveas_pattern=${ItemID}/${RevisionID}

Which in Teamcenter 2005 (10) is stored in the database, found from Portal at: Edit -> Option… ->  Search (tab on bottom)

But what if your UGMASTER, UGPART, UGALTREP or other datasets have different naming conventions? Lets say you add a ‘Drawing’ text into the naming. The Save-As will fail. So to fix this you need to add DATASET specific saveas_pattern. This example is for UGPART datasets:

UGPART_saveas_pattern=${ItemID}-Drawing/${RevisionID}

Think of the DATASET_saveas_pattern as the global rules, and the specific dataset patterns as overrides.

Force Drafting Settings into Template Files

Posted on Dec 4th, 2007 | 4960 commentshttp%3A%2F%2Fplmexchange.net%2Fforce-drafting-settings-into-template-files%2FForce+Drafting+Settings+into+Template+Files2007-12-05+03%3A19%3A34adminhttp%3A%2F%2Fplmexchange.net%2Fforce-drafting-settings-into-template-files%2F

 I noticed this in NX5, with the file new dialog has templates to choose from to base your part off of. By default there is a ‘blank’ file which will work as desired, but what if you had a set of english and metric files; Assembly, model, and analysis files. That is a lot of template files to be constantly updating. The interesting thing to note is when you create a new file based on one of these files, the settings that are part specific also go along for the ride. This is good and bad. If your drafting settings for example need to be tweaked, do you really want to change each and every one of these files? I don’t, so I’m glad to see NX has a setting in the customer defaults to override what is in the part.

In the customer defaults:
Drafting -> General -> Drawing -> Drawing settings -> use Settings from standard (option)

Knowledge Fusion optional variable arguments

Posted on Jan 16th, 2007 | 4900 commentshttp%3A%2F%2Fplmexchange.net%2Fknowledge-fusion-optional-variable-arguments%2FKnowledge+Fusion+optional+variable+arguments2007-01-17+03%3A06%3A27adminhttp%3A%2F%2Fwww.tolsnet.com%2Fplmexchange%2F%3Fp%3D490

An optional argument ia defined by parenthesis (), and one or many
optional arguments are defined with … (three dots).

Example would be to have optional many arguments:

Defun: Average (Number … $nums)

This example if a function called “Average” with optional arguments of
type “Number” that can be one or many stored in a list called “$nums”.

One way to access the $nums is by creating an expression block:

@{
$total << loop {
for $num in $nums;
sum $num;
};

So in Knowledge Fusion it is possible to have a function with optional arguments and it is possible to have a function to allow one or many arguments. The design patterns I try to stick to does not have a need for variable arguments but the optional feature is nice if you can have default values then override if necessary.