1 of 1 people found this helpful
Hey Emily -
I haven't bumped into your problem with punctuation myself, but I see that you're not wrapping the /views.. URI in double quotes. Have you tried that? The encoding that you're doing looks good.
Hi Russell- Thanks for the suggestion, but that doesn't seem to do the trick. I have submitted a support request.
Emily - this got me curious and I just poked around internally a bit. I found a support case that says we normally can get away with encoding the "usual suspects" (spaces, ampersands, backslashes, etc...)...BUT the comma and question mark cannot be part of a filter value, even if encoded.
Suggestion was to create a calculation which does a search/replace for the "bad" character ( , ?) with something else, then use that calculated expression in your filter.
How about a period?
Do you have an example of how the calculation might look?
Thanks for looking into this!
I didn't see periods mentioned as things you couldn't deal with - but they should be encoded.
Here's an example that looks at a field/dimension named "Complex", and replaces a "," symbol with "-"
IF FIND([Complex], ",") > 0
THEN LEFT([Complex], FIND([Complex], ",") - 1) + " - " + RIGHT([Complex], 2)
Russell - I am getting a strange result. In the filter result I used above, this calculation is giving me a result of "1900 C" Instead of "1900 VQC" which I am expecting as a result.
Sorrry - this is just an example - not necessarily to be re-used verbatim.
You'll notice that the expression is simply taking the final two characters from the right (RIGHT([Complex], 2)
You'll probably want to replace this with MID to take take the characters after the replaced symbol and add them ALL in vs. just the last two characters...ala mid([fieldname], find([fieldname], ",", 100) -- take 100 characters at the point where you find a ","
Sorry, I'm not the best with these types of calculations. Thanks for all of your help!
How do you handle the ampersand within tabcmd? Like handles a variable like %20Ham%20&%20Cheese?
Russell, I see that this response is from 2012, would you happen to know if this is still the case? I'm currently having the same issue and was wondering if it had been reolved, or I have to rename the values in my parameters.