Absent Member.. thePITman Absent Member..
Absent Member..
44 views

Validation "lookup_type" is Misspelled - How? And its link to User Data

I have a validation called "SCR - Configuration Types". When I create a new record in the validation, the value in the "lookup_type" column of KNTA_LOOKUPS_NLS in the database is entered as "SCR - Configuraton Types" (missing an "i" in Configuration). I found that, in the definition of the validation in KNTA_VALIDATIONS_NLS, the "validation_name" column is spelled correctly as was entered on the validation form, but the "lookup_type" column is misspelled (exactly as shown above, missing the "i"). It appears this "lookup_type" column value is what is being passed to the INSERT into KNTA_LOOKUPS_NLS when saving a new record in the workbench validation form.

 

In a development environment, I executed an UPDATE statement against the definition of the validation in KNTA_VALIDATIONS_NLS, correcting the spelling in "lookup_type" to match the "validation_name" and see if it would successfully save the record when I added a new one in the form. However, once I made this change, I no longer have the ability to enter User Data on the validation item, as the User Data tab became grayed out after the UPDATE statement.

 

So, I have a few questions, answers to which would help resolve my issue:

 

(1) How does the "lookup_type" column in KNTA_LOOKUPS_NLS get populated when creating a new record in a validation? Is it coming directly from "KNTA_VALIDATIONS_NLS.lookup_type" as I suspect?

 

(2) How would the "lookup_type" column get misspelled in KNTA_VALIDATIONS_NLS in the first place? I do not see anywhere on the validation form, other than the validation Name, that would logically get saved to this column. The values on the form are spelled correctly, so I'm trying to find out how the "lookup_type" column is populated.

 

(3) How can I correctly UPDATE the "lookup_type" column in KNTA_VALIDATIONS_NLS yet still maintain the User Data relationship? I appear to have lost the User Data relationship after running the UPDATE. I'm guessing there are other tables in the database that link to the "lookup_type" column, so would I need to make this change in several places? If so, what are the User Data tables (and any other tables) that also need modified?

 

(4) What are the watch-outs I need to keep in mind when considering direct changes to the tables listed above? Or is there a way these values can be updated through the workbench so as to avoid directly updating the database? (Note: I only did this direct update in a development environment. I did NOT do it in Production.)

 

I am attaching a document with detailed screen shots and troubleshooting steps I took.

 

Thank you.

0 Likes
1 Reply
Natalia_R_PPM Absent Member.
Absent Member.

Re: Validation "lookup_type" is Misspelled - How? And its link to User Data

Hi thePitMan

 

 

I see that you have a PPM support ticket open for this subject. I will work with the backline engineer to resolve the issue and then post the solution to this forum thread.

 

Also, I will investigate about this issue and replicate the problem.

 

 

Thanks

 

Best Regards,

Natalia Rojas

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.