From your screenshot, it looks like you want to pass a range to a variable value. This is not currently possible with URL parameters. There is an Improvement Request to implement this, which has been accepted, and the last update is that it will come in the Q4 release.
For now, you can only pass single values or multiple values. Depending on what you are trying to achieve exactly, and what control you have over the solution, you could adjust your BW Query to rely on separate From and To variables. You could also perhaps build an array of dates for the full range and pass these as multiple values, but it is not very scalable, and you may rapidly run into URL character length limits or related problems.
The best workaround for now, if you just want to open the query in Data Analyser (not specifically a saved insight) would be to call the openDataAnalyzer() method on a table using the live model in your Story. This will pass the range variable values to data analyser without you needing to script anything else. The drill state of the resulting insight will mimic the drill state of the table in the story, and all variable vaules as well as filter values will be passed also. It also passes the context, so if the end user saves an insight from the resulting data analyser view, they will also have the option to Save and Pin the insight to the source widget, so that they can come back to it again directly from the same story (pinned insights are user-specific, users will only see their own pinned insights).
If you wanted the insight to be in a different navigational state, then you could use a hidden table with a pre-configured navigation state, and call openDataAnalyzer() on the hidden table.
Cheers, Ivan.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.