Hello Peter,
I haven't tried the above code. I am assuming from your post that you're familiar with this sort change, and that it works on your other custom fields?
It is possible that there may be some problem around list_kd forms. You didn't mention your version, but here's an example of the sort order being wrong in the same area of code:
--------------------------------------------------
PRODUCT: Unicenter Service Desk RELEASE: 12.6
PROB #: 2733 FN: T52P089 FT: D33 DATE: 17 Jan 2014
STARTRAK PRODUCT NAME: USRD (Star Problem Product)
PROBLEM SYMPTOM: AIX-SEARCHING FOR KNOWLEDGE IN SCRATCHPAD MAY NOT
----------------------------------------------------
When searching for knowledge via the scratch pad
,if the character length of text is greater than
1499 characters , instead of displaying results
,it displays the search filter.
Steps to Reproduce:
1. Login to the web interface as an analyst.
2. Open the Service Desk tab
3. Go to 'View' -> 'Quick Profile'
4. On the 'Scratchpad' text box of the 'Quick
Profile' , enter a text containing more than 1499
characters.
5. Click 'Search Knowledge'.
Result: Knowledge Search filter is displayed
instead of result list.
UPDATED ROUTINES:
---------------
NOTE: For UNIX Script Files, the actual file size may be less than
the size shown below.
list_KD.htmpl 52303 FRI JAN 17 12:13:29 2014
list_KD.htmpl_tagged 54046 FRI JAN 17 12:13:29 2014
list_KD.xml 10257 FRI JAN 17 12:13:29 2014
--------------------------------------------------
I know it probably doesn't match your version or platform, and that the text itself refers to a different problem, but having a look at an issue it was attached to, it was a "similar" space that it was operating in.
So, barring someone else trying out your code on these Communities and responding (Which you're welcome to do), I suggest:
* Confirm similar change works on another field, another form. ie Your basic code works.
And/or:
* Try on a test box on a different version, if you have one available.
And/or:
* Log an issue to CA Support for your version/platform, and request a search be done against the list_KD patches for that platform. Cross reference to this post.
Then test with the latest code line. If your test case is as simple as above, you may even be able to convince an engineer to try it on their platform and consult with Software Engineering, even though we don't support customisations. Say "Kyle sent you."
Best to comment on prior steps when you raise the issue.
Thanks, Kyle_R.