Title: Bubble.io: VendorProfile is created, but User’s vendor_profile field remains empty
Hello Bubble Community,
I am building a healthcare marketplace called Doctor30Day in Bubble.io. I need help debugging an existing signup workflow.
The problem:
-
Hospital and Diagnostic Center users can sign up.
-
A VendorProfile sometimes gets created successfully.
-
The VendorProfile’s owner_user field can correctly reference the new user.
-
However, the User’s vendor_profile field remains empty.
-
The vendor dashboard depends on Current User's vendor_profile.
-
The workflow also has a condition that checks the Hospital signup result, which may prevent Diagnostic Center signup from creating its profile correctly.
What I need help with:
-
Identify why the User’s vendor_profile field is not being linked.
-
Check whether workflow action order or “Only when” conditions could cause this.
-
Suggest the safest fix without breaking Patient signup or Admin access.
-
Explain how to test the fix in Development before deploying it.
I am not looking to rebuild the app. I want to understand and fix the root cause in the existing workflows.
I can share screenshots of the relevant workflow actions and database fields, with private information hidden.
Thank you!
Well, I’ll try and answer this as best I can…
but honestly, my first thought was that you have this workflow so over-engineered that it’s confusing Bubble and cancelling itself out with all the ‘only when’ conditions.
You’ve got 14 steps.
From what I can figure out from what you’re wanting to do, I think this can be done in 5 steps.
Step 1: Sign the user up. Either set their role or leave it blank.
Step 2: Create a new vendor profile. Result of Step 1. Vendor type will be the result of the sign-up value. With an only when of ‘Dropdown DdVendorTypeSignup’s value is not empty’.
Step 3: Make changes to a thing. Result of step 1 sign the user up. The vendor profile will be the result of step 2. Only when the result of step 2 is not empty.
Step 4: Hide the modal.
Step 5: Redirect them where they should go based on their role.
It’s best to keep workflows as simple as possible and not add a ton of conditionals and steps that really aren’t needed.
Anyway, this is the best I could figure out based on your post and screenshot.
A useful distinction here: VendorProfile.owner_user and User.vendor_profile are separate fields. Saving the first doesn’t automatically populate the second.
Before restructuring the workflow, I’d run one Hospital signup and one Diagnostic Center signup in Development, step by step. At the action that sets User.vendor_profile, check:
- Which User is being changed?
- Does the exact profile-creation action referenced by that assignment have a non-empty result?
- Does its ‘Only when’ evaluate to yes for that vendor type?
Your Hospital-result condition is a good place to investigate: if the Diagnostic Center branch creates its own profile, a later action referencing the Hospital branch’s result could be skipped or have no profile to assign. That’s a hypothesis to verify in the debugger, rather than a confirmed diagnosis.
Also check the saved User record in App Data. If the link is saved there but looks empty on the dashboard, investigate field visibility/privacy rules separately rather than changing the signup logic.
For regression checks, use dummy Development accounts for both vendor types plus Patient signup and an existing Admin login. Confirm the two vendor links point to each other, each signup creates only one profile, and Patient/Admin permissions stay unchanged.
A cropped screenshot of the action assigning User.vendor_profile, including its ‘Only when’ and referenced step, would help narrow this down. No real patient information needed.
Yes, that’s what I said…
and even gave them the 5-step workflow to fix it 
