During some of our migrations, we get just the most recent part in, in the first pass, then load all the prior iterations at a later date. Our part loader was written to allow this, by using VersionControlHelper.service.insertNode when loading out of order, and it worked fine for the last few years. The one problem we just ran into just a few weeks ago was that if a prior rev has a describeBy link, it will not allow a more recent rev to be loaded.
So the scenario is:
- Load part 123A456, rev P.
- Load part 123A456, rev M.
- Load the describeBy links to both M and P.
- Load part 123A456, rev N - it fails here because of the describeBy link on rev M.
I'm updating the loader and was going to add a quick remove link/save new part/reapply link, if we're loading out of order, but I swore there was a preference, OOTB, that allows you to create prior revisions.
