👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact firstname.lastname@example.org
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact email@example.com
Thanks for your feedback :)
I was wondering if you could clarify a few things for me so I can ensure I understand your feedback:
 Can you clarify what you mean by multi-value fields? Are you talking about multi-select functionality - where the user can select multiple options in the dropdown?
 I'm a little unclear on this one too. Could you perhaps provide an example?
 Adding sort functionality to our connectors is on the backlog
 Yes, also called multi select. See mockup example below.
 Let me try to attach a sample.But again: it's just a mockup.I put in all the option settings I think that should be in.
To account for both multi and single-selection data lookups (assuming multi-selection lookups get added), this could return a collection of objects, where each object contains all the row data for that selection.
Making it configurable which columns are returned in this object would be even better, though I would assume this would rely on the system being queried to have an endpoint for the response schema.
For now you have to use this workaround, which works for a sharepoint list.