Not recognizing latest revision as latest! 9.1 M060

[gkemner]

We have had two instances now since upgrading to 9.1 M060 where
Intralink does not recognize the latest revision as being the latest
revision!

Here is what happens, revise a part from "Rev A Released" to "Rev B
Concept" but when you go to the details page for Rev B and it indicates
that it is not the latest. You choose "Go to Latest" and it takes you
to Rev A details page!



In the workspace Rev B Concept show as being "Out of Date". You do a
file update and it replaces "Rev B Concept" with "Rev A Released"



However, Pro/E will interpret the latest rev correctly. If go to an
empty workspace, do a file open in Pro/E and just type in the part or
drawing number you get Rev B Concept, however again if you check the
status in workspace it will show that "Rev B Concept" is out of date.
If you then do an update you get "Rev A Released"



I have tried modifying Rev B checking it in, promoting it and releasing
it and it still shows Rev B as being out of date and points to Rev A as
the latest, even though the modification dates are correct.



This is creating a lot of confusion with the users because when they do
an "Update" in their workspace they end up with previous revisions of
parts instead of the latest revisions that they were working on.



Any thought?!?

[sdrzewiczewski]

I believe there is a fix for this. Log a call with PTC. I had a similar
issue where it wasn't reporting the newest revision as the lastest.

> We have had two instances now since upgrading to 9.1 M060 where
> Intralink does not recognize the latest revision as being the latest
> revision!
>
> Here is what happens, revise a part from "Rev A Released" to "Rev B
> Concept" but when you go to the details page for Rev B and it indicates
> that it is not the latest. You choose "Go to Latest" and it takes you
> to Rev A details page!
>
>
>
> In the workspace Rev B Concept show as being "Out of Date". You do a
> file update and it replaces "Rev B Concept" with "Rev A Released"
>
>
>
> However, Pro/E will interpret the latest rev correctly. If go to an
> empty workspace, do a file open in Pro/E and just type in the part or
> drawing number you get Rev B Concept, however again if you check the
> status in workspace it will show that "Rev B Concept" is out of date.
> If you then do an update you get "Rev A Released"
>
>
>
> I have tried modifying Rev B checking it in, promoting it and releasing
> it and it still shows Rev B as being out of date and points to Rev A as
> the latest, even though the modification dates are correct.
>
>
>
> This is creating a lot of confusion with the users because when they do
> an "Update" in their workspace they end up with previous revisions of
> parts instead of the latest revisions that they were working on.
>
>
>
> Any thought?!?
>
>
>

[MikeLockwood]

We had that exact issue going from 8.0 to 9.0 - resolved by a patch. Message: Left-over relationship issues from Intralink 3.x migration, primarily involving the definitions of "latest" more than one level deep for skeleton-driven assemblies, esp. involving family tables of the assemblies.

You're essentially out of business until you get the patch and apply it.

[avillanueva]

I am using M020 and think I've seen the same issue. I have a call open
with PTC right now. What I saw was actually not different revisions but
within the same version. I was loading Parts from spreadsheet and it
was doing its validation checks against the first iteration, not the
last. Is this similar to what you were seeing? This was just WTParts,
not cad docs and the workspace.

Please post SPR or patch details if you know them.

[raimondas]

I observed the same issue in custom Java code.

At some point I figured that the problem is in QueryResults.

My custom Java code was giving me incorrect results. "the latest iteration
of the latest revision was not latest".... sometimes.
The problem that I found was/is with QueryResult data type.
which is supposed to be Ordered list of objs and last element is latest
iteration of latest revision.
but it was/is not..
I was not able to figure out the pattern and what Objects cause it.

Of Course I logged the call and they(PTC) said "no no" the last element is
latest and always is.
Again the issue was random and I was not able to replicate when I wanted so
we closed the call and I did quick and dirty workaround:

workarround
loop through queryresults content
and cheking mydoc.getVersionIdentifier().getValue().hashCode()

assumption is that hashcode() should return higher number for later
iterations.
so the object that holds max value of all hashcodes is latest iteration of
the latest revision
also assuming QR contains ONLY all Revisions and all iterations and nothing
else
(exact match in Search)

Had no issues with code since then.

Also I tried to catch in UI but was not able too.

Raimondas

On Tue, Nov 9, 2010 at 8:21 PM, Villanueva, Antonio <
-> wrote:

>
> I am using M020 and think I've seen the same issue. I have a call open
> with PTC right now. What I saw was actually not different revisions but
> within the same version. I was loading Parts from spreadsheet and it
> was doing its validation checks against the first iteration, not the
> last. Is this similar to what you were seeing? This was just WTParts,
> not cad docs and the workspace.
>
> Please post SPR or patch details if you know them.

[avillanueva]

Yep, similar to what I saw. I too traced is back to the
VersionControlHelper service. AllVersionsof() method I think. Should
return latest iteration of all versions in order. I swear that when ixb
code was processing, it was working on an id (ida2a2) of a WTPart that
was not the latest. I suspect that I saw a similar issue with Move and
Purge. Good to know, thanks.

[gperasso]

All,



This issue can also occurs on Familytables Intances. Depending on operations
made (checkout, undo revise ?) of a non complete family table



The latest EPMSepFamiliyTables (which role in the Data Model is to ?join?
the Generic iteration with the corresponding Intances) is not coherent?.



Resolve case by case by the PTC Support by generating a SQL script to
?rejoin? the EPMSep with the correct instances and generic ?



For WTParts, we can?t identify directly a ?latest?. because of the View
Network. Some parallel branch can be built. You should work in a particular
context (example, latest in the DESIGN view ?)



Regards

Gregory







De : Villanueva, Antonio [