ALM Setting default version of file to 1
Question ID: 108153

We had an upgrade this past weekend from 11.52 to 12.53…After the upgrade some Domains\\Projects are defaulting the version control to version 1 even when multiple versions exist. It should be setting the current version to the latest. When checking the files out a user may not realize this and lose work. Is there anyway to update this?

Marked as spam
Posted by (Questions: 89, Answers: 0)
Asked on February 1, 2018 1:02 am
Answers (1)
Private answer

ALM is checking out first version of VC entities like tests, reqs, test resources, etc. instead of latest one.

By using a query like the following we are able to determine what is the latest check-in version of an entity: i.e. test plan tests.


For example, If wrong value is shown under TS_VC_VERSION_NUMBER (i.e. 1 instead of 5) ALM will check-out version number '1' which is not the latest one!

VC entities like Reqs, Test Resources, etc might also be affected by this so the query should be modified to accommodate to specific entity table.


max(TS_VC_VERSION_NUMBER) from td.HIST_TEST table is not matching TS_VC_VERSION_NUMBER as set on td.TEST table


Fix For Tests:

Update td.test set TS_VC_VERSION_NUMBER = (select max(TS_VC_VERSION_NUMBER) from td.HIST_TEST where test.TS_TEST_ID=HIST_TEST.TS_TEST_ID) where TS_VC_STATUS = 'Checked_In'

Fix For Requirements:

update td.REQ set RQ_VC_VERSION_NUMBER = (select max(RQ_VC_VERSION_NUMBER) from td.HIST_REQ where REQ.RQ_REQ_ID=HIST_REQ.RQ_REQ_ID) where RQ_VC_STATUS = 'Checked_In'

*For any other affected entity/table make use of the above queries as template and modify accordingly.*

Marked as spam
Posted by (Questions: 0, Answers: 309)
Answered on February 1, 2018 1:06 am

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top