QR code opens url with recordId but the record is not known

Ask the community
1

Hi, I’m using Softr Database with an Item Details block for a public certificate page.

My setup:

  • Custom domain: app.certsafe.co.uk
  • Page URL: /public-certificate
  • “Find record by” is set to “Record ID in page URL”
  • Certificate URL formula is:

CONCATENATE(“https://app.certsafe.co.uk/public-certificate?recordId=”,{Record ID})

The page loads correctly, but when opening a certificate URL or QR code it says:

“Record details can no longer be found”

What is the correct URL structure required for Softr Item Details blocks to load a record from the URL?

Am I passing the Record ID incorrectly?

2

@imluke the URL is correct can you share an example where it doesn’t work ?

3

Thanks Artur.

Example failing URL:

When scanning the generated QR code it opens the public-certificate page but shows:

“Record details can no longer be found.”

The page is connected to the Certificates table and currently using “Record ID in page URL”.

I’ve attached screenshots of:

  • the error page

  • the page settings

  • the Certificate URL formula

Any idea what part of the setup is preventing the record from loading?

4

Hi Artur,

Just following up on this as I’m still experiencing the issue.

The challenge is that I’m building a compliance platform where each certificate needs a permanent public URL that can be attached to a QR code. At the moment I’m struggling to reliably link individual records/certificates to their own public page.

Could you advise the recommended Softr setup for creating permanent public record URLs that can be accessed from QR codes?

I’m happy to provide screenshots or a short screen recording if that would help.

Thanks.

5

@imluke can you give me example URL or QR code really want to test it to see how come it doesn’t load it’s very basic use case and as long as the URL contains valid recordId it should work just fine

6

@imluke — same issue tripped me up: double-check the record is still in the Certificates table and that the page isn’t restricted by visibility rules (logged-in only, wrong user group, etc.). Public detail pages need the record published and the block scoped to the same table. Worth testing a fresh recordId copied straight from the table URL bar, not a formula field that might store a display value. Hope Artur can repro — permanent QR URLs are a legit compliance use case.