When using immediate search in a DB Lookup within KTM Thin Client Validation, the columns are calculated on base of the column headers' length and not on the length of the returned result
As there is not a final solution available as per now, the workaround would be to start the search again from within the dialog window.
Level of Complexity
|KTM Thin Client Validation||6.4||18.104.22.168|
Add any references to other internal or external articles