Recent searches
No recent searches
error "Invalid conditions.Error: "You must select at least one condition." when attempting to create a view via the API using Zapier
Answered
Posted Apr 19, 2022
Hello! I'm hitting the error "Invalid conditions. You must select at least one condition." when I attempt to create a view via the API using Zapier.
However, i THINK i have a correctly formatted "All" condition for "Status."
Any thoughts on where I'm going wrong?
0
9
9 comments
Greg Katechis
Hi Matt! I took a look at the logs for these requests and there is a lot of formatting coming over with these requests, which is causing the payload to be unprocessable. If this is being copy/pasted from somewhere else, I would recommend trying this by holding the Shift key when pasting this, which will send only the text, without any formatting.
Let me know if this resolves it for you!
0
Matt
Thanks Greg! I'm still running into the same issue after stripping the formatting from the text. Any other thoughts? Any details about the formatting you're seeing that might be a clue?
0
Greg Katechis
I would try the same through Postman or curl and see if the issue persists from there. If it doesn't, I would reach out to Zapier and see if they're doing any html desanitization that might be causing these issues. If it doesn't work through Postman or curl, let me know and we can figure out our next steps here!
0
Matt
Thanks again Greg. I'm still getting the same response through Postman, even when sending it explicitly as text:
0
Greg Katechis
0
Greg Katechis
"position": 3
, which effectively closes off the payload. Since it was ending the payload before "all", we were receiving the error that said "you must select at least one condition." I cleaned it up for you here and tested this in my account and it created it appropriately. I would recommend using shift + paste when putting this into Zapier to ensure that any formatting from our code editors doesn't cause any more issues for you. Let me know if this works!0
Matt
Great catch! But i'm STILL seeing that same error. Do you see anything different in the latest logs?
0
Greg Katechis
0
Greg Katechis
0