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
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.
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.
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?
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).
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?
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.
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!
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.
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.
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:
This is a Public App - no credentials
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.
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.
@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.)
