Exactly this Sven, yeah. Thanks for clarifying.

That's wierd, when you search for folders, you should be able to include "documents" in the fields key and get the docs in those folders. What does your query string look like?

I would invert your logic and find all of your folders, instead of the documents, and include the list of documents on the returned folders.  

So just to make sure, there is a field where they select a number, and then you need to create a CSV with a new entry for each number formatted as    Name #, Date #   If that's correct, here's what I would do.   Setup a repeater that will repeat for how ever times they selected.Setup a text aggregat...

If you are still struggling with this, another option is to add a router right before your iterator, and put after thing you want to run once after your iteration is complete on a new leg coming off of the router.

Right-click on the route and select un-link.

You can get it, but not from the original object. Once you have the value you want, you should be able to make a request to the POPT end-point, parameter:name = {field}, and value = {value}.

You have to decouple the routes that you want to move down in priority, then re-link them in the order you want them to process.

You can do the same trick here as in your other post, Nick. If you can get your source information into a single array, like if you use a custom api call instead of the native one, you can use the deduplicate(map({your array};emailAddr))

Since it looks like you're feeding that array into an iterator, you can make your owner ID list without the iterator with this function in a variable.   deduplicate(map({your source array};ownerID))