RareEarth
Computer
- Nov 15, 2010
- 21
thread561-193304
Hi All,
Continued.. thread561-193304
I have extension to this question, even I am looking for similar thing but not able to achieve by using NX7.0 with master model concept. Any kind of help will be appreciated.
1. I need to call few attribute from UG Master to UG Part.
2. Assume that name of master part is "ABC" and attribute title "CREATED_BY" with value "BOB".
3. I can call this by <WABC@CREATED_BY> which is totally correct.
Problem comes when I clone top level file to new name or substitute child part with different name. Value of point 3 is now incorrect.
4. Now we have one more function available to fetch master part name by <W@$SH_MASTER_PART_NAME>
Q. Can we use both these function together to over come above mention barriers.
For example something likes <W<W@$SH_MASTER_PART_NAME>@CREATED_BY>
Or something <W$SH_MASTER_PART_NAME@CREATED_BY>
Were <W@$SH_MASTER_PART_NAME> will fetch master part name and this value will be used by second function.
Thanks in advance.
AS
Hi All,
Continued.. thread561-193304
I have extension to this question, even I am looking for similar thing but not able to achieve by using NX7.0 with master model concept. Any kind of help will be appreciated.
1. I need to call few attribute from UG Master to UG Part.
2. Assume that name of master part is "ABC" and attribute title "CREATED_BY" with value "BOB".
3. I can call this by <WABC@CREATED_BY> which is totally correct.
Problem comes when I clone top level file to new name or substitute child part with different name. Value of point 3 is now incorrect.
4. Now we have one more function available to fetch master part name by <W@$SH_MASTER_PART_NAME>
Q. Can we use both these function together to over come above mention barriers.
For example something likes <W<W@$SH_MASTER_PART_NAME>@CREATED_BY>
Or something <W$SH_MASTER_PART_NAME@CREATED_BY>
Were <W@$SH_MASTER_PART_NAME> will fetch master part name and this value will be used by second function.
Thanks in advance.
AS