I meant a search-string with the pipe as delimiter of the values and not just the exported dimension-values. Personally I don't need this very often in QlikView itself. Quite common are such search-strings instead with outside-values from users who needs data/views to a certain dataset. Mostly they are coming as excel-list or per mail and I create then the search-string in excel - it just needs a few seconds with an excel-expression.
In your case I would use like above mentioned an action which does the selection do. Further I could imagine to avoid these selections completely by adjusting my expressions appropriately, maybe with something like:
The only time I've even considering copying and pasting was when I had a longer list of values from a customer that I wanted to research in my dashboard on a detail level sheet.
For that I created an input box tied to a variable. A user could just copy and paste a list from Excel without worrying about pipes or anything.
Then I had another variable based on that that added the pipes and whatnot.
Then I tied an action to a button that would apply the search.
But I never tested it copying from one object to another.
