Forum Academy Marketplace Showcase Pricing Features

User not saved in DB


I have a issue with my app recognizing that the user is logged in and get this saved in the DB.

  1. The user fill in a form with a list of inputs he needs to fill in. At this stage being logged in is not required yet.

  2. When he clicks on submit a workflow is triggered with as first step the log in process through a pop up being displayed

Form submission workflow:

Log in process:

Is the user not being saved / app doesn’t recognize that the user is logged in because in the log in process it changes page? (steps 3 & 4). How can make sure that the process goes as follow:

  1. user logs in 2) the user is logged in and the step 3 (Create a new quote) includes the user currently logged in?

Thanks for the help!

  1. Do you have stay logged in set to yes here?

  2. Create the field “user” in the quotate, and
    and add the current user to it?

Thanks @makara .

  1. Yes the user will stay logged in
  2. It works but then creates 2 entries in the DB. One for the User and another one for the input form fields. The fields with the red cross shouldn’t be empty and the first DB entry shouldn’t exist

Any other ideas?

Perhaps it’s because you’re doing “create a new quotate” twice.
Can you change the one you are doing later to “make to changes quotate”?

It unfortunately doesn’t work as the login is a repeating group (pop up) with it’s own workflow and the form submission is another workflow.

How come step 3 taking place after the user logged in doesn’t recognized that there is actually a current user logged in on the platform? :thinking:


Is it possible to see the design of each?
“Not recognized” means that the current user does not appear as an option. Is that what you mean?

Oh, I’m sorry, I sent you some weird content.
The correct answer is.

  1. from the login button, navigate to the form input page. there, use data send “result 1’s(login) user” and use the current page user in the form input.

  2. Instead of “create by”, create a new field “user” and add the current page user to it.