REST query parameter keeps adding %EF%BB%BF

Jake Noyd
Giga Contributor

I've been trying to test a REST action and I'm fighting with a query parameter. When I run the call via curl I add 'return_records=true' after the path so that it returns some actual values and that works fine. In ServiceNow I'm adding that as a query parameter with return_records as the name and true as the value. When I test this it keeps inserting %EF%BB%BF after true which is screwing up the call. I've tried moving true into an input data pill as a string boolean but it still adds %EF%BB%BF. 

Anyone have an idea why it keeps adding this extra %EF%BB%BF and how I can avoid it?

1 ACCEPTED SOLUTION

Jake Noyd
Giga Contributor

Well this is resolved but without real answers. Our ServiceNow instance broke my test action. When I clicked on it yesterday to do some more testing it said "This action cannot be found" but it still shows up in the action list so that's fun. Anyway, I recreated the action but when I recreated it I didn't do the query parameters at all and I left off the second 'accept' header. I ran it and it worked. I don't have a clear answer as to why this worked with less data being passed. I wish ServiceNow gave me more information about what exactly it was sending like how Postman or Insomnia does. Maybe that is in there somewhere but I don't see it. Anyway, I hope this helps someone else. 

View solution in original post

5 REPLIES 5

kevclark
Tera Contributor

This seems to be a platform issue in Flow Designer - the Live Coding Happy Hour guys found it live on their recent TikTok episode: https://www.youtube.com/watch?v=-mtdrxK42AQ&t=2555s

Basically I've found that if you set a string input on a Flow Designer string input element it looks like the string will append the encoded characters.

I've been able to put together a "Steps to recreate" in a very basic flow designer subflow in the attached word doc.  I'm trying to get it logged with Support at the moment.  

I'm assuming it might be something that the browser might be doing - maybe a chromium update or something?  I found it appears on Chrome and Brave so far.

I've been able to recreate on Quebec and San Diego so far.

 

EDIT:  I've confirmed that it appears to be done in the browser, and appears to affect chromium browsers (I've recreated in Chrome and Brave).   I haven't been able to recreate it in Safari, so that leads me to think it must be a chromium problem.  My Brave is running Chromium: 105.0.5195.127 (Official Build) (arm64) on a Mac OS Monteray M1 Macbook Air (if Support is looking here 😉 )