HD46312: RENAMING THE INSTANCE NAME OF A PART BY SCRIPT IS DIFFERENT W H EN DOING IT VIA CATSCRIPT OR VISUAL BASIC

APAR status

• Closed as Permanent restriction.

Error description

• Renaming the instance name of a part by script is
  different when doing it via CATScript or Visual
  Basic.
  .
  The external References are not updated.
  .
  Scenario :
  .
  The following adjustments in Tools Options are
  important:
  .
  - Tools Options > General > Infrastructure > Part
  Infrastructure > General
  (see pic. 1)
  - Tools Options > General > Infrastructure >
  Product Structure > Nodes
  Customization (see pic. 2)
  .
  1. product1.CATProduct is loaded in Catia (is Root),
  see pic. 3
  2. Start Macro1.CATScript
  3. The Macro renames the instance name of part1
  (part1.1) to ?renamed.1?
  4. The External Reference in part2 is renamed
  automatically by Catia
  (see pic. 4)
  .
  .
  5. Close and load the product1.CATProduct again
  (see pic 3) or click
  undo button until the instance name ?renamed.1? is
  renamed back to the
  original (part1.1)
  6. Start the Visual Basic Application. The source
  code is identic to the
  Macro1.CATScript source code
  7. Result is shown in pic.5.
  .
  The External Reference in part2 is still
  the old one and NOT renamed. Collapse the node
  of External References (pic. 6) and expand it again
  (pic 7.)
  8. Save, close and load the product1.CATProduct
  again (see pic. 8).
  The External Reference in part2 is destroyed (the
  Link is shown in the Desk
  as Link with :No Status)
  .
  

Local fix

Problem summary

• Renaming the instance name of a part by script is different w h
  en doing it via CATScript or Visual Basic
  Renaming the instance name of a part by script is
  different when doing it via CATScript or Visual
  Basic.
  .
  The external References are not updated.
  .
  Scenario :
  .
  The following adjustments in Tools Options are
  important:
  .
  - Tools Options > General > Infrastructure > Part
  Infrastructure > General
  (see pic. 1)
  - Tools Options > General > Infrastructure >
  Product Structure > Nodes
  Customization (see pic. 2)
  .
  1. product1.CATProduct is loaded in Catia (is Root),
  see pic. 3
  2. Start Macro1.CATScript
  3. The Macro renames the instance name of part1
  (part1.1) to ?renamed.1?
  4. The External Reference in part2 is renamed
  automatically by Catia
  (see pic. 4)
  .
  .
  5. Close and load the product1.CATProduct again
  (see pic 3) or click
  undo button until the instance name ?renamed.1? is
  renamed back to the
  original (part1.1)
  6. Start the Visual Basic Application. The source
  code is identic to the
  Macro1.CATScript source code
  7. Result is shown in pic.5.
  .
  The External Reference in part2 is still
  the old one and NOT renamed. Collapse the node
  of External References (pic. 6) and expand it again
  (pic 7.)
  8. Save, close and load the product1.CATProduct
  again (see pic. 8).
  The External Reference in part2 is destroyed (the
  Link is shown in the Desk
  as Link with :No Status)
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  CATIA.
  This functionality is not available in batch mode.
  Use CATScript only.
  .
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels