# \[Solved\] Firebase automatically deletes previous tags when I upload new, different ones
**URL:** https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008
**Category:** Questions about Thunkable X
**Tags:** firebase, solved
**Created:** [July 11, 2019, 4:51pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008 "2019-07-11T16:51:24Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@maxb](https://community.thunkable.com/u/maxb)
#### Post date: [July 11, 2019, 4:51pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/1 "2019-07-11T16:51:24Z")
Hello everyone,
I’m uploading a ‘complex’ structure made of different objects to firebase:
but when I upload a new entry, a new “Ordine …blablabla” even if it’s different from the previous one it deletes the preexisting one, why?
Help please
---
### Author:  [@samclever](https://community.thunkable.com/u/samclever)
#### Post date: [July 11, 2019, 5:04pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/2 "2019-07-11T17:04:56Z")
It would have to be uploaded as Ordine del (change the date) and then it should save it. If you try and save a new value under the Ordini/Ordine del 11\7\2019 delle Ore 18:38 it will just replace the Ordine. It would also help to see a screenshot of the blocks that are saving to firebase.
---
### Author:  [@maxb](https://community.thunkable.com/u/maxb)
#### Post date: [July 13, 2019, 10:57am UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/3 "2019-07-13T10:57:10Z")
It’s a different ‘Ordine del…’ it changes the hour
---
### Author:  [@samclever](https://community.thunkable.com/u/samclever)
#### Post date: [July 14, 2019, 6:50am UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/4 "2019-07-14T06:50:34Z")
That is odd. And it is only changing the child node Ordine?
---
### Author:  [@maxb](https://community.thunkable.com/u/maxb)
#### Post date: [July 14, 2019, 6:08pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/5 "2019-07-14T18:08:08Z")
I was probably using objects in the wrong way (I knew it was too good to be true 😢).
If I save every firebase entry one by one, using **_set cloud_** _pattern_ to _value_
or **_db save_** , it works
---
### Author:  [@bymaho](https://community.thunkable.com/u/bymaho)
#### Post date: [October 1, 2019, 11:03pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/6 "2019-10-01T23:03:00Z")
I dont want “total” child to be disappered when I update only “location” child. I dont want to use much more blocks to solve this. Is there an easy solution for this? @actech @jane
---
### Author:  [@actech](https://community.thunkable.com/u/actech)
#### Post date: [October 2, 2019, 8:20am UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/7 "2019-10-02T08:20:33Z")
If you change the location node, the total node will not be changed. It’s like a file. If you are in Windows Explorer change the name of the selected file, it does not affect files that are next to it.
---
### Author:  [@bymaho](https://community.thunkable.com/u/bymaho)
#### Post date: [October 2, 2019, 12:24pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/8 "2019-10-02T12:24:57Z")
Can you open up your answer please. I didnt understand. Im sorry
---
### Author:  [@actech](https://community.thunkable.com/u/actech)
#### Post date: [October 2, 2019, 6:51pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/9 "2019-10-02T18:51:15Z")
To change the node values in the database firebase you need to specify the path to that node. You know what is the path to the node firebase?
On your way to figure coordinates as follows:
location/lat
location/long
If you specify such a way that total node will not be overwritten.
---
### Author:  [@bymaho](https://community.thunkable.com/u/bymaho)
#### Post date: [October 2, 2019, 8:53pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/10 "2019-10-02T20:53:52Z")
Thunkable is visual platform. Its hard to visualize a solution when you try to explain a person who doesn’t know nothing about programing like me. That’s why I put the solution down here. @actech thank you for godsend solution.💯
---
### Author:  [@ioannis](https://community.thunkable.com/u/ioannis)
#### Post date: [November 8, 2024, 12:08pm UTC](https://community.thunkable.com/t/solved-firebase-automatically-deletes-previous-tags-when-i-upload-new-different-ones/140008/11 "2024-11-08T12:08:47Z")