cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X

Reteam not allowed because the object is not the latest iteration. Refresh the data and try again.

MG_10170125
10-Marble

Reteam not allowed because the object is not the latest iteration. Refresh the data and try again.

Hello,

We have error in windchill "Reteam not allowed because the object is not the latest iteration. Refresh the data and try again."

I can't any information about this error. All I understood about this error is that it happens with new objects in windchill. I can upload these new objects to workspace but can't check in.

1 ACCEPTED SOLUTION

Accepted Solutions

So, its been some time, still having an issue? That is a very specific message but I can understand it being triggered if you are trying to change the team on a non-latest iteration. You can only do that from latest iteration. You said this was new items so things that have not been checked in yet. CAD docs or WTParts?  There should be a message in the MethodServer logs that would be helpful if you could post it.

 

Are there any listeners or customizations in play that would be trying to modify data behind the scenes as its create but before check in? Another question is this across the board for all users, all context or just sometimes? It could be something with Object Initialization Rules, maybe. Say you upload to one context but try to check in to another that has a different team setup in the OIR definition. Could that cause the behavior? @MG_10170125 , need more info on what you are seeing.

View solution in original post

6 REPLIES 6

 Hi,

 

The following article may help - "How to checkout and checkin non-latest iterations of objects in Windchill": https://www.ptc.com/en/support/article/CS22588 

Thank you! I will try it but this error about new objects in windchill. They only exist in the workspace.

 

And if it work I will need to manually switch the allowing checkin non-latest iteration settings on every error.

 

I would like to know the reason for this error.

 

So, its been some time, still having an issue? That is a very specific message but I can understand it being triggered if you are trying to change the team on a non-latest iteration. You can only do that from latest iteration. You said this was new items so things that have not been checked in yet. CAD docs or WTParts?  There should be a message in the MethodServer logs that would be helpful if you could post it.

 

Are there any listeners or customizations in play that would be trying to modify data behind the scenes as its create but before check in? Another question is this across the board for all users, all context or just sometimes? It could be something with Object Initialization Rules, maybe. Say you upload to one context but try to check in to another that has a different team setup in the OIR definition. Could that cause the behavior? @MG_10170125 , need more info on what you are seeing.

Many thanks! User really try to upload to one context and then check in to another. We could simulate and resolve this problem.

It happens with CAD docs (.asm, .prt and .drw), not with WTParts.


We will observe more, perhaps this has always been the cause of the error.

 

 

 

 

Great, you can mark this thread as resolved and accept solution. Recommend making your team defined in your CAD Doc OIR at the org or site level which will avoid this case from happening.

I don't see any info about this specific error either - and have never seen it in 25 years of CAD admin.

 

Are you attempting to modify a non-latest version or is it something else?
Re-team seems like a very odd message for CAD data - the default Team assigned to every object by OIRs makes sense for change objects, but is usually empty for CAD.

 

Can you supply us any more info?

Top Tags