Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello
Given the following data:
Queries:
load * inline [
subject,form,value
'100-100-100','Lesion Assessment - New Lesions',1.0
'100-100-200','Lesions assessment -New Lesions',2.0
];
and a sheet with the following table:
If I create a hyperlink to open my app to the above sheet and select one of the form names using the template:
http://{server}/sense/app/{app id}/sheet/{sheet id}/state/analysis/options/clearselections/select/form/{form}
this link only applies the proper selections when I specify one {form} or the other by itself. When I specify both forms, delimited with semicolon, selections are only applied when at least one form name is enclosed in square brackets. In other words (url encoding omitted for readability),
/form/Lesion Assessment - New Lesions selects 'Lesion Assessment - New Lesions' as expected
/form/Lesions assessment -New Lesions selects 'Lesions assessment -New Lesions' as expected
/form/Lesion Assessment - New Lesions;Lesions assessment -New Lesions only selects 'Lesions assessment -New Lesions'
/form/Lesions assessment -New Lesions;Lesion Assessment - New Lesions only selects 'Lesions assessment -New Lesions' (showing that order doesn't matter)
/form/[Lesion Assessment - New Lesions];Lesions assessment -New Lesions selects both.
/form/Lesion Assessment - New Lesions;[Lesions assessment -New Lesions] selects both.
Why would having both of these values specified on the URL require at least one of them to be bracketed when each works perfectly well by itself? And no, I can't automatically bracket all values because too many brackets on a URL appears to cause Qlik server to timeout trying to apply the selections so I need to bracket only those things that absolutely need bracketing. Thus I'm trying to determine logic for what I must bracket and what can omit brackets.
Regards,
Steve
Looks like results are unpredictable if the needed syntax is not met. As I see in the documentation, it expects each value to be bracketed -
Thanks for the pointer. I've actually experimented with doing a blanket bracketing of every value. Unfortunately, for very long URLs with lots of values, bracketing everything can result in a "search timeout" error. In contrast, I've actually gotten very good response times when I only bracket those items that absolutely need bracketing, like values containing "/". The difficulty here is determining exactly which values require bracketing, especially when that requirement appears to change depending on what other values are in the URL.