A similar Solution attached.
What is the length of your policy number. Qlik Can handle quiet big amount of data.
Search Via Inputbox.qvw 261.5 K
Did a test (still running) and first conclusion is that variable content seems to be limited only by available RAM. At the moment, my variable contains a continuous string of about 100MB.
- Available RAM as the only limit is pretty unpredicitable as the maximum content depends on the situation, and you'll never know when stuffing too much data in a variable will fail eventually...
- Functions that you apply to a variable may become very slow because of the size of the data. Even QV internal operations may start to experience slowdowns.
I think there must be better ways to tackle a problem like this.