Forum Discussion
My bad on suggesting to put + instead of %20, it generally works if you put the query parameters directly in the URI field.
I gave it a try, see the below screenshot.
where ever in your query you’ve space leave them as it is, it’ll be translated to %20 and same with other special characters.
“INSTALLED_SW_LAST_CHANGE_TIMESTAMP get ”+Date.now().toLocaleDateString()+“T15:00:00-05:00)”
For me, it worked fine when I removed the %20 and + from the filter string.
Hope this helps.
Cheers
I am facing still same issue when I pass filter criteria in REST GET snap .
But when I try in edit pipeline and passing same filter criteria it works (all formats are working, %20,space and +)
I am not sure at this point why same filter criteria is not working when given REST GET snap ☹️
- Abhishek_Soni373 years agoContributor
This is weird indeed, can you try to put everything in the Service URL and try it? Don’t pass them via query parameters[Although it should work].
If TIMESTAMP value is hard coded in service URL it works, but if same value given in query parameter it doesn’t work .