Showing results for 
Search instead for 
Did you mean: 

In Session chnages to NX part


Hello ALl


I ha ve a scenario


User1 and USer2 both open a Part in NX from TC


  1. User1 checkout the Part and start working on it, while USER2 has same Part in session (READ ONly), he still keep working on the part just to see the how the part looks with chnages without saving it
  2. User 1 now CHECK IN The Part
  3. User2 who was working in Readonly, relaises  that he like to save his changes, so he checkout the part (from NX manager ANT) and Try saving the Part


Do you guys think above is valid scenario, if so how you folks handle it.


I got this kind of issue reported by one user, an di dont have a answer how we can avoid it






Re: In Session chnages to NX part

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
Look into "Explicit Checkout" by disabling implicit checkout. Then users would be forced to check out before they receive write/change permission. It answers the "trying to save a read-only part" question by making it clear that a prior checkout is required to save a part. It incurs a small penalty on users by forcing them to checkout parts instead of the system trying to take care of it for them. If the penalty is acceptable then configuring explicit checkout is your solution.


There are advantages and disadvantages to each solution. The business will have to pick the lesser of two impacts on performance.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4