APAR status
Closed as Permanent restriction.
Error description
PROBLEM: Using publication in a CATScript causes ERROR mesaage. . SCENARIO: 01. Open the CATProduct: CONTEXT_PROBLEM 02. Activate the CATPart: Plate 03. record a macro as CATScript: name Hole_1 - make a Hole to one vertex of the published Sketch.2 an the upper surface of PAD.1 04. stop the macro 05. delete the Hole 06. run the macro: Hole_1 (the Hole comes up) 6a. delete the Hole 07. record a new macro as CATScript: Hole_2 - make a Hole to one vertex of the published Sketch.1 an the upper surface of PAD.1 08. stop the macro 09. delete the Hole 10. run the macro: Hole_2 . RESULT: A massage appears saying -- > "AddNewHoleFromRefPoint" method failed. . EXPECTED RESULT: The macro for creating second hole should work as in case of first hole. .
Local fix
Problem summary
Using publication in a CATScript causes error message when running a recorded macro PROBLEM: Using publication in a CATScript causes ERROR mesaage. . SCENARIO: 01. Open the CATProduct: CONTEXT_PROBLEM 02. Activate the CATPart: Plate 03. record a macro as CATScript: name Hole_1 - make a Hole to one vertex of the published Sketch.2 an the upper surface of PAD.1 04. stop the macro 05. delete the Hole 06. run the macro: Hole_1 (the Hole comes up) 6a. delete the Hole 07. record a new macro as CATScript: Hole_2 - make a Hole to one vertex of the published Sketch.1 an the upper surface of PAD.1 08. stop the macro 09. delete the Hole 10. run the macro: Hole_2 . RESULT: A massage appears saying -- > "AddNewHoleFromRefPoint" method failed. . EXPECTED RESULT: The macro for creating second hole should work as in case of first hole. . Best Regards, CAA Maintenance. .
Problem conclusion
THIS PROBLEM IS PERMANENT RESTRICTION IN CATIA . Incident Diagnosis When using a macro to make an hole using a published element the feature Brep is KO. . Restriction Explanation Macro use the alias name of Feature to create Feature Brep ( this is not the case in live). If this name is not good the FB could not be created and the macro is KO. I our case 2 features have the same name Datum.1. The 1st feature is used, and the FB is KO. Nothing could be done to prevent this. But step have been added in order to have different names on the feature. . By-Pass If you delete and re-create the import of published sketch the naming will be good and macro will be usable. .
Temporary fix
Comments
APAR Information
APAR number
HD78529
Reported component name
CATIA V5 NT>XP
Reported component ID
569151000
Reported release
517
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-07
Closed date
2009-05-05
Last modified date
2009-05-05
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"517","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
05 May 2009