ALM lookup list in ALM is displaying values intended for another field.

Question ID: 110054
1
1

Hello. We have a ‘Subject’ field in ALM that is displaying values in the lookup list that are only suppose to display for the ‘Environment’ field. I have check the customization, and it has the correct list selected for the ‘Subject’ field, so I am not sure what is going on. Have you experienced this issue before. Thanks!  

Marked as spam
Posted by (Questions: 230, Answers: 30)
Asked on January 29, 2021 4:01 pm
7 views
Answers (1)
1
Private answer

Hello. I have seen this before, and I was able to revolve the issue by performing the following steps. I ran the folowing query on a customer project, where this exact issue was occurring. After running the query, I ran the 'Verify' and 'Repair' on the project, and the lookup list was back to normal for 'Subject' field. The issue was due to a corruption that occurred in the TS_SUBJECT and BG_SUBJECT fields within the project data tables, and the query below sets them back to where they are supposed to be. Before running the query below, it is highly recommended that you create a backup of the affected project repository and database in case any unforeseen issue occurs. You will run the query against the SYSTEM_FIELD table for the affected project. After you have run the query, verify, and repair on the affected project, retest to see if the issue still occurs.

UPDATE SYSTEM_FIELD

SET SF_ROOT_ID =

(SELECT ALM_ITEM_ID

FROM ALL_LISTS

WHERE (0 = 0)

AND AL_DESCRIPTION LIKE 'Enter_your_folder_name_here'

AND AL_FATHER (0 = 1)

WHERE (0 = 1)

OR SF_COLUMN_NAME LIKE 'TS_SUBJECT'

OR SF_COLUMN_NAME LIKE 'BG_SUBJECT'

After you have run the query, verified and repaired the project, run the following query to make sure the values displayed in the SF_ROOT_ID field for BUG and TEST have been corrected.

SELECT SF_TABLE_NAME, SF_COLUMN_NAME, SF_ROOT_ID

FROM SYSTEM_FIELD

WHERE (0 = 1)

OR SF_COLUMN_NAME LIKE 'TS_SUBJECT'

OR SF_COLUMN_NAME LIKE 'BG_SUBJECT'

Marked as spam
Posted by (Questions: 2, Answers: 292)
Answered on January 29, 2021 4:03 pm
After running the query, and performing the steps you suggested, the issue has been resolved. Thank you for your help!
( at January 29, 2021 4:03 pm)