# URL parameters / URL strings

**URL:** <https://community.glideapps.com/t/url-parameters-url-strings/73131>\
**Category:** Ask for Help\
**Created:** [May 6, 2024, 10:19pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131 "2024-05-06T22:19:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkbw](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mkbw/32/74637_2.png) [@mkbw](https://community.glideapps.com/u/mkbw)\
**Post date:** [May 6, 2024, 10:19pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/1 "2024-05-06T22:19:28Z")

</div>

It looks like retrieving URL parameters or query strings into form fields or directly into the table is something that a lot of customers have been asking for for years now. Has anything changed?

I cannot find it documented here or elsewhere in official documentation if it has. It appears that Glide has the ability to construct them when a form is filled out but unable to capture them? [Construct URL | Glide Docs](https://www.glideapps.com/docs/construct-url)

In my use case where I need to encode data on a public form like a UUID for Customer ID in a foreign system so that I can connect the actual form input to my IPaaS (Make) and create a draft/provisional customer order. I intend to encode the URL strings into a QR code that takes users to the Glide form. In my case the only form field that I want a user to interact with is uploading photos.

Any work arounds? It sounds like a disaster of typos and other garbage data to have users enter this data manually. Alternatively the dropdown list would literally consist of nearly 500 choices just for one customer.

Rather frustrated.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [May 6, 2024, 10:23pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/2 "2024-05-06T22:23:20Z")

</div>

> [@selfie Populate a Form by Scanning a QR Code](https://community.glideapps.com/t/populate-a-form-by-scanning-a-qr-code/69957):
>
> v Hey fellow Gliders! In this video, learn how allow users to scan a QR code to prepopulate a form screen using: point_right A helper table point_right A template column point_right Get Part of URL columns point_right Form container I’ve used this method to create scavenger hunt activities, inventory apps, onboarding functionality, and time card systems. There are several of variations you can do using this methodology (eg. use a form screen over a form container, create QR codes…

---

<div class="post-metadata">

**Author:** ![mkbw](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mkbw/32/74637_2.png) [@mkbw](https://community.glideapps.com/u/mkbw)\
**Post date:** [May 6, 2024, 10:33pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/3 "2024-05-06T22:33:34Z")

</div>

I discovered this [Get Part of URL column | Glide](https://www.glideapps.com/plugins/url-parts) and there’s a great walkthrough here [Using URL Parameters to Filter a Collection | Loom](https://www.loom.com/share/cb256cdbba8c4cb4aa16cef983d0fb1d)

So it is possible… with “experimental code”

---

<div class="post-metadata">

**Author:** ![mkbw](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mkbw/32/74637_2.png) [@mkbw](https://community.glideapps.com/u/mkbw)\
**Post date:** [May 6, 2024, 10:38pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/4 "2024-05-06T22:38:21Z")

</div>

Thanks @Jeff_Hager

I stepped away and came back thinking there’s got to be a way to do this I’m just not searching effectively and found that Get Part of URL plugin on my own. I will certainly watch this video to learn how you handled this within Glide.

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [May 7, 2024, 5:30pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/5 "2024-05-07T17:30:49Z")

</div>

@mkbw - This thread might help?

> [@How to pass parameter to glide apps?](https://community.glideapps.com/t/how-to-pass-parameter-to-glide-apps/40090/14):
>
> WTF? exploding_head …great tip!! I had seen/tried the Get Part or URL plugin before, but hadn’t found a proper use case for it, but “The URL of the current screen” parameter changes everything. [image] Thanks for the video and your time Darren. Feliz día!.

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 6, 2025, 7:09pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/6 "2025-01-06T19:09:04Z")

</div>

It seems that “The URL of the current screen” is no longer retrieving URL parameters. Do you know if this is a bug in the current Glide platform or an intentional limitation introduced by the Glide team?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 6, 2025, 7:18pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/7 "2025-01-06T19:18:05Z")

</div>

How do you have your column configured?

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 6, 2025, 7:50pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/8 "2025-01-06T19:50:03Z")

</div>

The URL is formatted as follows: `glideapp.url/dl/activity?code=ABC`.  
The `ActivityCode` column is configured as shown in the attached image, and the column value is `<empty_string>`.

**Important** : This functionality worked correctly in the recent past (December).

 ![column config](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/b/eb62d9b89daef8a0860b77c2480bcced2a4fa69d.jpeg)

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 6, 2025, 8:51pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/9 "2025-01-06T20:51:46Z")

</div>

Column configuration looks fine.

I can’t seem to duplicate the issue. I trust you are actually navigating to the page with the query parameter included, or are you just typing it into the url bar and not hitting the Enter key to navigate to that url?

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 6, 2025, 9:28pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/10 "2025-01-06T21:28:08Z")

</div>

Yes:

> [@Jeff\_Hager](#):
>
> actually navigating to the page with the query parameter included

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 6, 2025, 10:01pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/11 "2025-01-06T22:01:20Z")

</div>

Hmm, I’m not sure what’s going on. Is it also a problem in the published app and on different devices? I guess I would try from a different browser or computer, or try clearing your browser cache.

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 6, 2025, 10:17pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/12 "2025-01-06T22:17:13Z")

</div>

This was a working functionality and suddenly all users started to have a dysfunctional experience.

I will try a simple test with a different app in order to see if it is an isolated or generalized issue.

Thank you Jeff for your kind support.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 6, 2025, 10:19pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/13 "2025-01-06T22:19:33Z")

</div>

Let me know what you find out.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 7, 2025, 1:21am UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/14 "2025-01-07T01:21:53Z")

</div>

> [@BDan](#):
>
> This was a working functionality and suddenly all users started to have a dysfunctional experience.

Still works as expected for me 🤷‍♂️

 ![CleanShot 2025-01-07 at 09.20.21@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/b/cb7f9ef109c42e4e0935f4eb528df1013e27864a.jpeg)

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 7, 2025, 9:21am UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/15 "2025-01-07T09:21:59Z")

</div>

Jeff, Darren, it seems that this specific functionality stopped working a few days ago (possibly around the New Year transition) for one of the older applications. Interestingly, the same functionality (extracting a portion of the URL from the current screen URL) works perfectly in any new test app. Since the issue appears to be specific to the older app, I’ve reported it to the Glide Support Team.

Thank you once again for your kind and prompt feedback!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 7, 2025, 9:35am UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/16 "2025-01-07T09:35:35Z")

</div>

When you say an older App, do you mean a Classic App?  
They are no longer supported, so if it’s broken I suspect that Glide won’t fix it.  
Anyway, let us know how you get on with Support.

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 7, 2025, 9:47am UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/17 "2025-01-07T09:47:45Z")

</div>

This is not a Classic App - it was developed in May 2024, making the appearance of this issue quite inexplicable in this context. I’ve reached out to Glide Support and will follow up here once I receive their explanation.

---

<div class="post-metadata">

**Author:** ![mkbw](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mkbw/32/74637_2.png) [@mkbw](https://community.glideapps.com/u/mkbw)\
**Post date:** [January 7, 2025, 2:24pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/18 "2025-01-07T14:24:04Z")

</div>

Hey @BDan I just tested an app that’s in production and this feature is working.

Obfuscated URL of how mine works:  
[https://request.mydomain.com/dl/xyz123?location=jLfsNRs1QUykjpymr9eZVw](https://request.mydomain.com/dl/xyz123?location=jLfsNRs1QUykjpymr9eZVw)

Are you sure that the user(s) are using this in a browser and not within a glide app (“PWA” progressive web app)?

In my case I have discovered that URL parameters are dysfunctional if the user followed the prompt to “install” the PWA app. Glide is not suitable for my app long-term because I cannot suppress the pop-up nor prevent users from installing a progressive webapp which causes me to lose URL parameter strings (breaks my app at step 5 below - there’s no location to relay). We’re moving this app out of Glide for this reason by the end of February. I need mobile users to only access this via browser because of the way URL parameters work within the PWA App.

My production app works like this:

1. This is a Public App - no credentials
2. User scans a QR code with a URL parameter string for location  
2a. The URL parameter string is the “Row ID” of _Locations_ table with columns (fields) with an address, phone number, contact, etc.
3. [https://request.mydomain.com/dl/xyz123?location=\*\*\*jLfsNRs1QUykjpymr9eZVw](https://request.mydomain.com/dl/xyz123?location=***jLfsNRs1QUykjpymr9eZVw)\*\*\*
4. User enters data into a Glide form
5. When user submits the location string is committed to the Location row in the _Requests_ table and lookup columns(fields) query the address
6. A REST API POST then occurs generating an order in a foreign system (this could be the same app or another glide app)

Like I mentioned above it works and works well as long as the user doesn’t install the “app” but if they do the URL parameter is lost.

---

<div class="post-metadata">

**Author:** ![BDan](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@BDan](https://community.glideapps.com/u/BDan)\
**Post date:** [January 7, 2025, 2:39pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/19 "2025-01-07T14:39:19Z")

</div>

Hello @mkbw, thank you for the detailed response.

The application might be installed as a PWA, but the issue also occurs when it is used in the browser, a scenario that is more relevant for me.

The usage scenario involves a user wanting to share a Glide link (a link containing filtering parameters) via WhatsApp. That link should then direct another user to a page displaying specific content based on the parameters in the link.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 7, 2025, 3:31pm UTC](https://community.glideapps.com/t/url-parameters-url-strings/73131/20 "2025-01-07T15:31:09Z")

</div>

@mkbw just floating this out there… Wouldn’t you be able to share a QR code of the url from the ‘detail screen’ (or maybe a ‘new screen’ if you want to have a separate forward facing screen) from the location table for each specific location? That link already contains the rowID for the specific row. Then design the detail screen or new screen to do whatever you need it to do for your use case. I feel like you could avoid having to use query parameters and instead use the native url structure.

Are you trying to prevent users from navigating backwards to a list of locations, or something else? I think there are ways to mitigate that if that’s the case.

(I don’t think this would solve @BDan’s use case though.)

[Next page](https://community.glideapps.com/t/url-parameters-url-strings/73131.md?page=2)
