i usually find myself in this situation and was hoping this idea might be helpful for everyone
- What is your idea?
Add a flag "Share" to the "Save Current Selection" action in order to allow this saving to survive at the end of a procedure and to be recycled in other procedures.
- What specific problem are you trying to find a solution to, or what new scenario would this idea respond to?
- When finding a select through select based on is too slow to be applied in real time (performance)
- When a select should be shared through different processes (functionality)
- What workaround have you found and used so far (if any)?
We currently use cubes to store these information (dataflows) and "select based on" action to restore selections if needed. But this flag could save cubes and time.