Mike,
Usually the best case scenario is that if you can use the helper table but not depend on any of its look up values and instead create a bulk import set and some kind of for each loop the populates that bulk import set. That way the pipeline can run asynchronously.
But if you absolutely need those look up values once the focus is set for that helper table then it has to be a looping pipeline which calls itself. So that means the pipeline itself needs to be a callable pipeline where the first step in the pipeline is pipeline called. So then they would have to be a Nother pipeline which gets triggered to search a table for some records but return only one value from the search. When you create a search step you can limit the results to only X number of results so you could limited to the first result.
Then he would set the focus and call the pipeline which would use that helper tables value and then the next step in the Callable pipeline need to do something to trigger the search again which would still be limited to just return one value.
Of course you need to be doing something so that the search results are different the second time and that eventually there are no results returned from the search. There is a pipeline step you can introduce that can detect if a search returns no results.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
Qrew Legend
