NX Revision rule "Precise only" does not give expected result

An assembly, item revision A, have been created with two components, 000080-Block having item revision C and 000081-Cylinder having item revision B. The assembly is saved as Precise and is closed.





Later on 000080-Block is modified a saved as item revision D.
At this point, with the revision D of the component still in the NX session, the assembly is opened with revision rule "Precise Only".
The assembly is presented to the user with the revision D of the 000080-Block component despite the precise assembly having been stored with the revision C of the component. No warning/error message, nothing. This is not precise, it is something else.

Solution

This will happen with the standard NX customer default settings. 
There are a couple option that could be considered in this context under File --> Utilities --> Customer Defaults, Teamcenter Integration --> General, Multiple Revisions tab

• If you enable the option "Check Revisions on Load" you will get information from NX when opening the precise assembly when one or several of its components already is open in the current NX session, but in different item revisions than the one referenced in the precise assembly.
  
  
• If you enable the option "Enable Multiple Revisions" the precise assembly will open with the exact component item revision(s) as present when the precise assembly were stored. 
  In this situation there will be no information from NX even if "Check Revisions on Load" is enabled, as there are no conflicts. I.e. as multiple revision now are allowed several revisions of the same item can co-exist within the same NX session. 
  The D item revision of the 000080-Block component will no longer be forced upon later opened precise assemblies referencing revision C.
  
  

Notes and References

Hardware/Software Configuration

Platform: INTL64
OS: window
OS Version: 764SP1
Product: NX
Application: NXMANAGER
Version: V11.0
Function: FILE_OPEN

Ref: 001-8986437