I’m having an issue where any time I try to filter by a non-string table column (or property) I get an internal server error when I test my connector. I’ve tested filtering by my table column fjxcf_testing_order but also just by _sequenceNumber, and both result in a 500 error. Do I need to do some other treatment of the HTTP query to work with non-string filters or is this a bug?
Ah, of course I figure it out right after posting! Don’t put quotes around your filter “arg” value if it’s a number!!
Topic can be closed.
hello @Ethan, great to see you solved the problem!!
I will mention that you can also include the filter parameters in the Connect Function as such, rather than the URL which makes it easier to visualize in my opinion:
1 Like