Onboarding form not linking logged-in user to profile table

Ask the community
1

Hi Softr team,

I’m building a membership app using Softr Databases and having trouble linking onboarding data to the logged-in user.

Setup:

Members table (default Softr users)

  • Name

  • Email

  • softr_user_id

User Profiles table

  • User → Related record to Members (single)

  • City

  • Suburb

  • State

  • Postcode

  • onboarding_completed (checkbox)

Form setup:

  • Form connected to User Profiles

  • Action: Create record

  • “User” field:

    • Related record → Members

    • Hidden input ON

    • Value = Logged-in user

Issue

  • Profile record is created

  • But the related User field shows “Unnamed record”

  • Lookup fields (Name / Email from Members) do not populate

  • Linking feels inconsistent or broken

Questions

  1. Is using Logged-in user → related record the correct way to link profiles?

  2. Should onboarding data live directly in the Members table instead?

  3. Is there a required identifier (softr_user_id / record ID) I should be using?

  4. Any known limitations with Softr Databases + related user records?

Goal:
One clean profile per user, auto-linked on onboarding, no Make/Zapier.

Thanks!

2

@bird3382 Short answer to this is yes, this is happening, and the communication was weak.

There was no clear email or changelog call-out. Most people are only discovering it when opening blocks and seeing the “condition is no longer valid” message.

Legacy conditional filters still work for now, but this is a soft deprecation. Historically, these don’t break immediately, but they do get removed over time. If the block shows the warning, you should plan to update it.

There’s no reliable mailing list today for breaking or structural changes. That’s the real issue here, not the change itself, but the lack of advance notice.