URL Button formula and URLEncode() function

  • 1
  • 1
  • Question
  • Updated 1 year ago
  • In Progress
Looking for confirmation on Quick Base behaviors.

We have many URL formulas used as buttons to pass record ID#'s and relevant field ID#'s to child records. Recently the Formula help has started to point out any field that is wrapped in the URLEncode() function that Coach uses. 

Users have started to say the buttons aren't taking them to the correct form, we use dfid to point at separate forms. Also users are saying that when they click Save & Close it takes them to the child table home page, instead of returning them to the parent form page, this is done by using the Rurl() function.

I am finding that removing the URLEncode() function resolves the problems listed above. I want to know if anyone else who is using these features is experiencing a similar problem?

Thanks in advance
Photo of Jim Harrison

Jim Harrison

  • 1,926 Points 1k badge 2x thumb

Posted 1 year ago

  • 1
  • 1
Photo of Chris


  • 4,430 Points 4k badge 2x thumb
The only warnings my formula URLs give is when I pass URLEncoded numeric values to alphanumeric fields, which is legal. Seems it does not require numeric fields to be URLEncoded. My buttons still work fine however.
Photo of Matthew Neil

Matthew Neil

  • 31,698 Points 20k badge 2x thumb
I've never seen that issue myself.  I use the URLEncode for every variable that I pass in the URL, but not the dfid.

fid_6="&URLEncode([Record ID#]& "&dfid=10

Rather than relying on the "& Rurl()" function, you can decide the 'NextURL' that they go to after save.

....fid_6="&URLEncode([Record ID#]& "&dfid=10&NextURL(www.google.com)"
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,224 Points 20k badge 2x thumb
Generally, you only have to URL Encode fields or literal strings that contain the following characters:

! * ' ( ) ; : @ & = + $ , / ? # [ ]

So you never have to URLEncode a [Record ID#] as it contains only digits.