Warning: Versioning and tab pane very buggy in new Innovator versions!!! Are you affected?

Hi community,

I need your help to investigate an error that occurs in newer Innovator versions. In my case it occurred in Innovator 12SP17 and 12SP18 but NOT in Innovator 12SP7 / 9 / 10. 

I look for a bug fix for this one, cause unfortunately Aras rate this one as unimportant glitch and not as high risk behavior. From my POV the bug is a huge source for trouble (data loss!!), so I just can warn people to update to SP17 and SP18 without this bug fixed.
I want to investigate, which service pack version is NOT affected by this bug. I am not able to test out all available service pack, so I would be happy if community could help:

If you are a user of Innovator 12 SP11 / 12 / 14 / 15 / 16 / 17 I would be happy if you could test out at least the Error 1 scenario!! (2 minutes required!)


In 12SP17 and 12SP18 the tab pane can crash to easily when using item versions (like in Parts, Documents and Methods).
In addition, old item revision can overwrite the latest item without the user noticing it!
Both errors can occur easily, as soon users display previous revisions of an item. Comparing old and new revisions is a typical work during a Change Management process, so it´s an error that affects daily work of PLM users.

Test Setup

If possible perform this test in a test database. No data is edited during the test when you closely follow the instructions. But I don´t want to bring you in trouble in case of error!

1. Go to TOC -> Administration -> Open ItemType "Method" search grid
2. Search for Method with with "Ver 2" or higher, to ensure the Method has more than one revision.
   (If you need extra safety, create a temporary custom Method for this test that you can delete after test finished)
3. Open this Method (it doesn´t matter which one)
4. Open the 'Versions' dialog
5. Select a previous version (e.g Ver 1) of this Method
6. A Form with the previous version of your Method shall open.
7. Do not touch the new window with the previous version
8. Simply switch back to the tab with the newest version of the Method and close the "Versions" dialog

We now have both versions in parallel in the tab pane. This is our basic setup. So far everything is fine. 

Reproduce Error 1 (Tab pane crash)

1. Start from setup above. We are in the tab with the latest revision
2. Click "Edit" (but do nothing else)!
3. Now just switch back to the tab with the previous revision of the Method and simply close this window
4. After closing the previous revision, we will automatically jump back to our latest revision tab
5. Click "Discard" as we never wanted to edit anything
6. Now the error should happen:
In case of error a second tab reappears. We now have the two tabs for the item. They do not work and you cannot close them. Tab pane is crashed. Everything will be fine again after restarting Innovator in browser.
If you don´t see this error, your Innovator version is not affected by this bug. You can skip all other tests. Please share which version you used!

Reproduce Error 2 (glitch)

6. When you directly click "Search Method" in the TOC after above error occurred, a small additional glitch can appear
7. As our tab pane is crashed, the search grid will overlab with the Method Form. None of the tabs can be used reliable anymore

Reproduce Error 3 (previous revision overwrites latest)

Warning: Perform only in test database! Use a custom temporary Method for testing out this one, cause it can corrupt your data!!!

1. Start from setup above. We are in the tab with the latest revision.
2. First switch back to the tab with the previous revision. This time do not close the window, but simply take a look at the "Edit" button. It´s grayed out and you cannot use it. (This is correct behavior, as we never should be able to edit previous revisions)

3. Switch back to the latest revision and click "Edit"
4. Again switch back to the previous revision and take a look at the "Edit" button again. This time it´s not greyed out anymore!!!

5. It´s now theoretically possible to click the edit button inside the Form of the previous revision!
6. In case you click the 'Edit' button, you can create a high risk scenario:

7. After clicking the 'Edit' button, it´s seems to be possible to edit the previous revision. But what you see doesn´t represent the "truth" any more.

a) The shown Method code still shows the content of the previous revision
b) But the context item has switched to the latest revision. But this revision change is not visible to users as they still watch the previous code/properties. You can only see it in the 'Generation' value in the 'Properties' dialog.

If you now save your "fake" previous item, the latest item will be overwritten with code and properties of the previous version. This is a high danger situation not only for Methods, but for all ItemTypes that use revision as it will lead to data loss and corrupted data.


I discovered the bug while merging a few upgrade patches and actually destroyed a few Methods cause of this bug. If I as admin fail to handle versioned items cause of this behavior, I expect that real users will face the same problem soon.

I right would  not recommend to use 12SP17/18 just because of this bug. Comparing and working with item versions is a daily task especially when using Change Management. But it´s important that users can trust the data they see. Right now working with revision in SP18 is very risky cause users can crash their tab (best case) or overwrite data without knowing (worst case). 

Please let me know if you are able to reproduce any of the above bugs in your Aras Innovator version! If you´re Innovator version doesn´t show the bugs, please also write a short post! When we can determine in which service pack the error appeared first, it´s maybe possible detect the bug more easily.

Thanks for your help!


  • Hi Angela

    Thanks for this. I have tested above glitch in my SP18 instance and able repro this issues.

    Reproduce Error 1 (Tab pane crash) - Tab pane crashed

    Reproduce Error 2 (glitch) - In this case, when I click search able to see methods but when I click open it is opening in the same method search window

    Reproduce Error 3 (previous revision overwrites latest) - Agreed, able to see edit button in both the version. On edit of previous version, overrides the latest version.

    Thank You

    Gopikrishnan R

  • Hi Angela,

    I tested this out as well. I am on Aras 12 SP14.

    Reproduce Error 1 (Tab pane crash) - No crash

    Reproduce Error 2 (glitch) - Since there was no crash, no issues with search

    Reproduce Error 3 (previous revision overwrites latest) -  This did overwrite my latest version. Works exactly as you described.

  • Thanks Gopikrishnan and mczbas for your tests! I didn´t assume that parts of the bug already appeared in Aras 12 SP14.

    For people who do not use a lot of versioned items in Innovator (like Aras itself...) this one looks like a small unimportant glitch. But I really fear it side effects. I stopped all current work on updates cause it´s unclear if Aras will address the issue at all. There are many bugs that I can tolerate, but for me this one is really a showstopper.

    I did some debugging by myself. The problem are probably the tab ids. Innovator seems to use the same id independent from revision. A bug fix probably requires a couple of codetree files to be changed. I already have found related code files where the bug occurs, but it´s a bit tricky.

    It´s not even a surprising bug. It´s somehow typical Aras. Many applications at a certain level shows buggy behavior when versioned items show up (MPP, PE,...). Of course they test their application - but most of the time they never think about the use case that users may have an item version. It´s simply not in their mindset. So it´s up to us users to send them reminders until they finally learn.

    Do you have the possibility to address the issue to Aras too?

  • Hi community,

    I still want to address this topic and so I try to keep this thread visible in the forum.

    Has anyone of you already installed Innovator 14 beta (or Innovator 14 itself) and can check this one out? According to Aras there were a lot of bugfixes in I14 (like in every release), but haven´t seen the release notes yet. 


  • Hi community,

    an update on this one: According to the Innovator 14 release notes none of these bug have been fixed and they are NOT recognized as known bug in the software. Can somebody confirm that the bug wasn´t fixed? Did anyone else receive a feedback from Aras that somehow indicates that they are aware of the issue?

    A PLM software that has fundamental flaws in versioned items is a no-go. Sending users wrong feedback is a no-go. This bug is really a showstopper on many levels.

  • Hi community,

    happy new year everyone! I decided that one of my goals for this year is finding a solution for this issue. Maybe I will make even a video why I think this issue is such big danger to our data.

    Luckily I think a solution is not too far away. There are some "claim&edit" related topics on the roadmap. But I am not sure if they address the above topics ....or another one that I have seen as critical concept already 3 years ago Grin --> https://community.aras.com/f/community/4849/will-the-upcoming-innovator-12-edit-concept-lead-to-tons-of-nonsense-revisions

    Well, I learned to be patient. Was anyone of you an early-bird and has installed Innovator 15 already? I don´t expect the issue to be fixed in I15, but I still would be happy if somebody could test out!

    Best regards!


  • Hi Angela

    I tested this on 12 SP16 and the bug is in here too. The tab pane did not crash but the edit button is available on both version and the edit of the previous version overrides the latest one.

    Keep well.


  • Looking at the roadmap I've gained some hope that the bug was recognized. Unfortunately I haven´t received any official confirmation yet. I assume Aras is just a bit shy. Or they hope that I get impatient enough to patch it by myself (...just to release an official patch one day after...).

    Nevertheless, I want to keep the bug list as complete as possible. So here a few new scenarios related to this behavior.

    Reproduce Error 4 (Roadtrip to uncanny valley)

    1. Start from setup above. We are in the tab with the latest revision
    2. Click "Edit" (but do nothing else)!
    3. Then just click "Discard"
    4. Now just switch back to the tab with the previous revision of the Method 
    5. We now can see the green flag in the previous revision

    6. Click on the green flag to unlock the item

    7. Toolbar will get confused and we now get a nice grayed Save and Done button. 

    8. This bug is mainly an optical glitch. It doesn´t do much harm. I think it´s a nice extension to the above collection.

    Reproduce Error 5 (Lock seems to be the root cause)

    Here I start from the previous scenario, but have changed the Method ItemType. I extended the keyed_name so it combines the "name" and "generation" property. 

    1. Start from setup above. We are in the tab with the latest revision
    2. Use side-by-side mode for direct comparison of the items
    3. Lock the latest revision by clicking the "flag" -> Flag turns green
    4. Note that the previous revision will immediately change

    This image shows the result: Context item was updated on lock, but the Form still shows the previous content:

    I assume claim/unclaim is the root cause. Both events are fired when we try to edit an item. 

  • Hi community,

    it´s a new month and Aras released a new Innovator version --> 17 !

    According to the release notes and the roadmap they really fixed the "nonsense-revision" bug I reported 3 years ago: Grinninghttps://community.aras.com/f/community/4849/will-the-upcoming-innovator-12-edit-concept-lead-to-tons-of-nonsense-revisions

    In general the roadmap indicates that Aras slowly return to the right track. They even plan to integrate tab indicators (which I already use successfully since 2 years and several people have adopted the concept already. But I am happy to see that Aras finally wakes up and joins too..)

    But the big question remains: Will this improved edit behavior also improve the buggy behavior of versioned items? 

    Would be happy to hear your result if anyone had the opportunity to thest it in Innovator 17!