Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I had been working on the post : Re: search for values of a field on activate sheet which lead me to do some R&D and I found that concat() could not generate result beyond the length 2^16 -1 = 65535. Is this a known limitation?
I think you have hit the byte limit of a text value on the front-end.
Have you considered creating a child table with a record per word and searching that instead?
Thanks David for replying.
Might be you are right. But I am not very sure about the technicality of qlikview when it comes to front-end calculation. Alternatives could be explored. But I am more interested on it's explanation here. It could have been better if the technicality could be explained by authority. May be someone from qlik like Henric Cronström could shed some light.
Update: Just found another thread discussing same issue: Re: Limitation in Text Object of 65,535 Chrs!?
I would like to bring this on top of the stack once again.
In that case I think you would get a faster response by raising a support call directly with Qlik.
That's true.