I am able to pass the parameter from my dashboard to reports without any issues.
while I was testing I noticed that for few scenarios, I am not getting the expected results and when i relaunch the dashboard and try the same selection it works fine.
Try adding a label to the dashboard that will display the URL before you click the button. It is possible that some peculiar series of steps is writing different data than what you expect.
Do the expected values have spaces or special characters in them? Those can occasionally cause issues.
At the times it is not getting passed, is the URL in the label still good?
Do you have some way (e.g., Fiddler) to capture the URL after it has been passed? Can you tell which part is getting malformed?
If it is truly random, then you may be out of luck. It would come down to being “one of those things” where the dashboard is just not processing correctly. The solution in that case might be to have two different cells that both calculate the URL. If they don’t match, then don’t send the URL.
You say “a few scenarios” in your opening post. Is it totally random or are there some specific occasions when the parameter doesn’t pass? Some specific values or characters? Xcelsius doesn’t handle odd characters well - in the past I’ve had to extract both sides of an apostrophe and then join them back together afterwards!
Try breaking it down. If you are generating the value through user selection and then concatenating a string to pass out, do it in several cells. Sometimes for me, building the string in one hit has been unreliable, but doing it in stages worked.
(BOB member since 2005-03-01)