I would like the TABLE.EXTERNAL_RECORD_CONTENT_GET() function, when alphabetizing prior to using UNIQUE_KEY_VALUE(), to create a list considering upper, lower, and word spaces (doubt it can do this one easily).....Or have the Unique key value render its results differently so that these variants are considered.

Here is a list of "unique" words in a crlf list:
Notice the 3rd word is identical to the 1st and the 6th word is identical to the 4th. I see it as the initially the list is placed in alphabetical order without regard to case....and then the unique_record function does consider case....but THEN only for the previous value in the originally alphabetized list, not the entire list.


Dan Krag
dan Krag
Dan Krag
Dan krag
Dan krag
Dan krag
So either one or the other function could have another argument added (for backward compatibility).