When a new user creates an account, I need to copy the Firebase DB

Questions about Thunkable X
, ,
25

You mean for task2?
No those are not even being detected in the output

26

Can you share a screenshot of the output?

28

Screenshot_20210113-152628~2
Screenshot_20210113-152628~21413×1089 103 KB

I changed my default to !!! !!Default so it will always be at the top of my DB, I’m sure only 1 ! would have sufficed but it’s what I did

29

Sorry, you’re on your own on that one

30

You mean you don’t know why it’s not adding the task2?

31

I fixed my 5! so now default just says !Default. I was thinking for some reason in case the user’s email address started with more than one ! they would have a chance of being at the top of my DB in Firebase. But then I realized the userIDs which are created are specifically all alphanumeric

32

For some reason, when there’s a lot of data involved, this doesn’t update EXISTING users data.

I’ve tried it on a button press event and if I spam the button 4 or 5 times I can get it to update existing users, but if I just leave it on a ‘when screen opens’ component it won’t do it. I’ve tried putting in some wait 1 sec components all over the place during the function with no luck.

Any suggestions?

33

This is where I’m at for now with this…

If a user is missing a task, it will be added as intended, but it also reverts all the users other saved tasks back to the default, removing all of their progress…
Any suggestions?

image
image1730×1428 327 KB

34

From your blocks,

You are checking for the existence of the subtask and if Null then instead of creating the subtask you are writing back the whole task which will overwrite any existing subtasks along with creating the missing subtask.

35

Ok I see @muneer , all I needed to do was change the set property > subcatj and then also set it to get property subcatj of object categoryiesj of object mastertaskobject.

Thank you for your help.

Now at this point it is also checking every single user when 1 user logs in. It doesn’t need to do that, it only needs to be checking the current user against the !Default