Skip to main content
Question

URL Button formula and URLEncode() function

  • April 5, 2018
  • 0 replies
  • 205 views
JimHarrison
Forum|alt.badge.img+16
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

      • ChrisChris
      • Quickbase Alumni
      • April 5, 2018
      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.
      • MCFNeil
      • Quickbase Alumni
      • April 5, 2018
      I've never seen that issue myself.  I use the URLEncode for every variable that I pass in the URL, but not the dfid.

      i.e.
      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)"
      • anomDiebolt
      • Quickbase Alumni
      • April 5, 2018
      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.
        Terms & ConditionsAccessibility statement