Skip to main content
M
Milkman4-Participant
4-Participant
October 26, 2016
Question

Created Default Rep but can not activate or edit it.

  • October 26, 2016
  • 4 replies
  • 3399 views

I created a Default Rep in a part, but now I can not edit it, activate it, or even remove it. Anyone familiar with this problem?

4 replies

D
dschenken1-Visitor
1-Visitor
October 27, 2016

I am not aware the Default rep can be removed.

How are you trying to edit it? Have you been able to create other Part Simplified Reps?

M
Milkman4-ParticipantAuthor
4-Participant
October 27, 2016

I don't really want to remove it, I want to edit it. I thought maybe if I could delete it and recreate it, that might fix the problem.

I can not even activate it. I have tried Double_Click, Right click-Activate, Right click-Redefine, Edit-Redefine, I get nothing.

Yes, I have created other Reps, but this one seems to be corrupted from when I first created it.

M
MartinHanak24-Ruby III
24-Ruby III
October 27, 2016

Hi,

I think that your problem is related to your very specific part. Originally it was an assembly. The assembly was exported somehow and imported as single part. Then some external merge features were created. I guess that Default Rep is available in native assembly, only.

model.png

MH

M
Milkman4-ParticipantAuthor
4-Participant
October 27, 2016

The Default Rep was not in the native assembly though. I created this Rep after the import and merged features were added.

D
dcompton4-Participant
4-Participant
December 21, 2017

I'm having this same issue with an assembly that I created with a "save-as". It is driving me insane. Have you found a solution? 

joe_morton
18-Opal
joe_morton18-Opal
18-Opal
March 30, 2020

Came across this when we saw a similar issue in a part in Creo 4 M060. The user told me the part had been imported/exported several times between neutral formats and different CAD systems. 

We were able to add a new rep named "Default" and it seems that it overwrote the existing Default Rep, making it editable again. 

Thought I'd share in case someone else runs into this again

    Terms & ConditionsCookie settingsAccessibility statement