Thing not getting created in DB even though Unique ID gets generated

Need help Database
21

ok, I know you told me to quit with the cookie thing. But I just created a few customer needs without any problem but without being logged in. This is just my suggestion, but I would change the workflow as follows:

  1. User fills out form.
  2. User clicks “post need”. At this stage, no entry is made to the database. the only thing that happens is the log in pop-up is shown.
  3. User completes log in / sign up steps and clicks sign up.
  4. At this stage, sign the user up and then create their first need as the next step. No cookies needed :slight_smile:
22

And what if user drops off because of friction of logging in / signing up? I don’t want to lose them. I want to call them and see if we can do something for them.

23

Also that won’t work in case of social logins, as in case of social logins, page refreshes after logging in.

24

@mghatiya did you ever get a solid answer on what was the cause of the data not being correctly created? I have a similar issue, I create a new “thing”, I see the unique ID of the the thing in the debugger, but in the database view, a thing is created but it has a completely different unique ID. It the workflow for the page where it was created I update the thing, and no updates are reflected in the database and likewise, when I try to pass the thing to another page, the thing can’t be found. I put in a bug to support becuase this seems quite strange.

1 Like
25

No real answer I got for this. However, this was quite long back and I even stopped support for this use-case in my app as it was not working properly. Don’t know if things have changed now.

26

Thank you very much for your response. I was afraid of that. I sent a bug report to bubble.io tech support, I can reproduce it quite easily, along with a video. If I do get an answer, or a work around, I’ll post here.

27

I’m getting a similar error too. When I use the Debugger, I can clearly see the unique ID is what it should be, and the update should be made. But when I examine that thing in the database, the update has not been done.

This error is so basic and is preventing me from deploying my app. Worse: the error is intermittent: some days it happens, and other days it is fine…!