Spotfire Data Functions need to support native 'String List' type as inputs or outputs

Spotfire's Data Funcitons are among the top differentiators from its competitor tools and I use them often to create very valuable and sophisticated user work-flows that takes a complex process and makes it seem trivial.  In creating a specific workflow that leverages user inputs from 'multi-list' properties, I found a very unexpected problem.

Spotfire has a native 'String List' property (created automatically when creating a multi-list.  This property type is not supported in Spotfire's Data Functions.  The 'String List' is a very popular and valuable data type in native Spotfire and not being able to leverage in R, TERR, or Python causes users of Spotfire to limit what a designed work-flow can handle.  I don't consider myself a novice to Spotfire, and if I struggle to find a work-around to address this issue, I would expect the majority of people to struggle with it as well or just give up and determine that Spotfire's Data Function functionality is inconsistent with supporting Spotfire's native data types.

Data Functions need to have their own category and should not be lumped in with 'Advanced Analytics'