Skip to main content
B
BenLoosli23-Emerald III
23-Emerald III
March 14, 2022
Solved

How to delete a failed regeneration of an assembly point

  • March 14, 2022
  • 4 replies
  • 1918 views

We have an assembly where we have deleted some components but that has left behind some assembly points. These points cause regeneration errors and now we are trying to delete them, but there is no delete option. When opened in the Reference Viewer, the point shows no parent and no children dependencies, only a missing reference to a non-existent parent.

Anyone have any idea how to remove these point features from our model?

Best answer by sacquarone

Thanks @BenLoosli 

 

Thanks for having shared the reference. I downloaded your assembly, and I'm able to reproduce the issue in original conditions.

 

I do not share any video here, because you may not want to show things in the Community (not sure), but I was able to resolve the issue as follows:

  1. Select all DATUM Points in Model Tree (from APNT98 to APNT103)
  2. RIght click and access Group icon (observe creation of a Local Group)
  3. Right Click and Delete the Group

I nevertheless agree that there is something strange here (I do not see any valid explanation to justify wHY we need to create a Local Group first to delete those points), but maybe, if it's really an isolated case, above approach will allow you to consider this as solved.

 

Whatever your views after having considered above approach, Thanks in advance to share them with Sampath Betha (notified internally in parallel about existance of this post) who is cuyrrently handling this case C16295066.

 

Regards,

 

Serge

4 replies

tbraxton
tbraxton22-Sapphire II
22-Sapphire II
March 14, 2022

It is hard to diagnose without access to the models, but I can think of one thing to try.

 

Create empty parts with the names of the deleted components and add them to the assembly. Regenerate the assembly and if the points still fail. See if the option to delete them is available. If this fails, try to reestablish the dependency of the points to the dummy components by rerouting the references. I would use the default Csys in the dummy part if possible.

S
sacquarone21-Topaz I
21-Topaz I
March 15, 2022

Hello @BenLoosli 

 

I fail to find similar issues in our Knowledge Base. Whatever is Datum Point is issued from Point, Offset Csys or Field available approaches, they can always be selected (graphically, from Model Tree or using Search Tool) and then deleted. Therefore, the only possible options I see are as follows:

1. The presence of Datum Point is driven by definition in Pro/PROGRAM => If so, It's expected to not propose "Delete" or "Suppress" in the UI, The Program needs first to be modified to get rid from the definition impacting it

OR

2. The Datum Point is somehow corrupted => If so, as @tbraxton said, we'll need to access the impacted assembly to troubleshoot this further (+ eventual case to PTC TS if needs to be reported to R&D as a SPR for eventual diagnostic + data fix if possible)

 

Regards,

 

Serge

B
BenLoosli23-Emerald IIIAuthor
23-Emerald III
March 15, 2022

Support case was opened, C16295066, being addressed by Sampath Betha.

The assembly file was uploaded.

S
sacquarone21-Topaz IAnswer
21-Topaz I
March 15, 2022

Thanks @BenLoosli 

 

Thanks for having shared the reference. I downloaded your assembly, and I'm able to reproduce the issue in original conditions.

 

I do not share any video here, because you may not want to show things in the Community (not sure), but I was able to resolve the issue as follows:

  1. Select all DATUM Points in Model Tree (from APNT98 to APNT103)
  2. RIght click and access Group icon (observe creation of a Local Group)
  3. Right Click and Delete the Group

I nevertheless agree that there is something strange here (I do not see any valid explanation to justify wHY we need to create a Local Group first to delete those points), but maybe, if it's really an isolated case, above approach will allow you to consider this as solved.

 

Whatever your views after having considered above approach, Thanks in advance to share them with Sampath Betha (notified internally in parallel about existance of this post) who is cuyrrently handling this case C16295066.

 

Regards,

 

Serge

    Terms & ConditionsAccessibility statement