Sorry if its a stupid question: I have to update 2 “fields” under a “master key” in Firebase, but when I save it using the “create object with fields” all the other data under the same key is deleted. Because is a long list of fields, do I need to put all the fields in order to preserve all the da…

Reading a lot about Realtime Firebase, I understood that data are kept there as JSON. And that means that even if we (and by “we” I talk about me and others used with row/columns/fields data type organization) see it as a structure that looks like fields, in fact under a key there is an organized ob…

When I’m doing something like you try to do, first step for me is to retrieve data from Firebase using a variable and get block… this way an object with the same structure as my firebase is created. Next step, ill change only the data i need to be changed in that variable… In your case, something …

Not a stupid question at all! I prefer to use cloud variable names for this instead of the Realtime DB blocks. In fact, this is recommended by Thunkable in the documentation. You would do set cloud variable [join] where [join] is the join block you have above but you would need to join “STATUS” as…

Yeah… I understand this approach… but the point here is that unfortunately you will need to “read before write”, consuming time and network… For apps that are critical and with massive use, this will cost a traffic overhead… That’s why a looking for a direct approach, or the other way is to change…

I found no lag in using this method by reading-writing to Realtime Firebase, that is running extremely fast at least for me… And my app is handling a lot of data aswell: [png] … and i have alot of "fields just like this of length of thousands chars… And i retrieve data instantly… at a cost of o…

I swear I’m trying to learn how to use cloud variables for other purposes than only store ID sequences :slight_smile: But in the case I have a “customer” master key (/CLIENTES), under this customer key I have other sub-keys like “contracts” (/CONTRATOS), and each new contract receive your own ID (…

@tatiang I don’t see how to create dinamically this kind of variable in Thunkable X… I see that this type of block is allowed only in the new version… correct? So, I will need to move all my project to the new version to use this type of declaration of cloud variables or there is a way to do it in…

Thunkable X is the current and only version of Thunkable available right now. I think what you are asking is if this can be done in the older “Snap to Place” (StP) interface instead of the newer “Drag and Drop” (DnD) interface. In both interfaces, you can find it near the bottom of the variables dr…

You are right! It’s just because I was looking for the “initialize” block to declare the variable with the “join” structure… but if the SET block works, so let’s do it :slight_smile: Thanks!

Saving partial data below a Firebase key?

Questions about Thunkable

tatiang October 29, 2021, 7:58pm 5

Accessing stored variables can be slow so I recommend setting the app variable UserID to stored variable UserID and then using app variable UserID when accessing Firebase.

Saving information into the database

Topic		Replies	Views
Create and Save Data in Firebase Questions about Thunkable firebase , beginner , help	11	1764	April 17, 2023
Connecting cloud variables to firebase Questions about Thunkable	14	1770	November 8, 2024
Guardar actualizar y eliminar datos con la variable nube Questions about Thunkable	33	1208	July 13, 2022
Replace GET or SAVE Blocks with cloud variables Questions about Thunkable firebase , solved , asynchronous , json , cloud-variable	29	3427	November 8, 2024
Realtime database Questions about Thunkable	2	260	November 8, 2024

Saving partial data below a Firebase key?

Related topics