just to be sure now your output should be different than “NULL” right ?
@pte yes,
I tried two different ways: one with a list of values also for the id and the other one without a list. But both don’t work during the running of the app.
The second one : record set as list of value and id as string only is the right one for your purpose. I never tried on an empty table, could you put some record in your table for example ? If still not working, could you name your variable result_array and not “result array”. It can help with programming 
@pte those are the names of my table
.
Also with result_array it didn’t work. There is still an error on the MAP_TO_TEXT trigger. Were you able to insert the object “record” in the Expression field?
In the expression editor you should be able to select MAP_TO_TEXT_LIST(variable.result_array.record,“id”) if the connector output is correct.
Below a screenshot of my connector output in variable :
@pte, it’s working ! thank you for your patient and help.
So the main problem at the end was that I used the type of an array instead of a variable to save the result in the “run connector function” trigger.
2 Likes
It’s been a while since this topic was active, but have the same issue as mentioned above.
TLS is set to yes, and API keys are filled in.
Output has been defined as list of objects, with dot as extractor.
Can anyone help here? @Beth ?
Hi Quintijn!
You could still use this approach from this thread, but honestly I think the simpler way to accomplish getting table records into a single/multi-select is to use a “unique values” aggregation and then use that aggregation as the data source in your single/multi-select. (At the time of this post, “Unique values” was not an aggregation option in the platform, hence why the connector approach here)
To see a walkthrough of how this would work, you can check out John’s post below!
Let me know if this helps, or if you prefer the connector option, we can debug that further.