# Help with cloning **URL:** \ **Category:** Questions about Thunkable X\ **Tags:** clone\ **Created:** [November 7, 2022, 5:12pm UTC](https://community.thunkable.com/t/help-with-cloning/2119681 "2022-11-07T17:12:26Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [November 7, 2022, 5:12pm UTC](https://community.thunkable.com/t/help-with-cloning/2119681/1 "2022-11-07T17:12:26Z")
I’m trying to clone a container within a layout (beta feature). The container has labels inside. I’m populating the labels from Firebase values. It’s working great to initially clone the first container and fill it with values. But if I run the function again with a different Firebase key (Journal/app variable date), it still populates the labels with the **initial** values. I can change the key (each key has unique values for item, time, and note sub keys) but it still shows only one set of values. It’s not updating as I intended. The Debug label shows the correct values. For example, if I set `app variable date` to today’s date, it will show the values from that key in Firebase. And if I change `app variable date` to yesterday’s day, it will show the values from that key instead. But again, the cloned labels will only have today’s values no matter what I change `app variable date` to. Any ideas why this is happening? Also, is there a way to do this without deleting all but the first container before cloning everything again? ![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/2/8/285832f501c604f53217cfeb654cf9e0b6cdf903.png) ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 7, 2022, 10:45pm UTC](https://community.thunkable.com/t/help-with-cloning/2119681/2 "2022-11-07T22:45:36Z")
> [@tatiang](#): > > Also, is there a way to do this without deleting all but the first container before cloning everything again? Place your master copy outside of the slave column. What’s it not working on. Mobile or web preview? ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [November 8, 2022, 12:05am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/3 "2022-11-08T00:05:52Z")
Thanks, I’ll try that. It’s not working on iPhone 11 Thunkable Live or browser preview. ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 8, 2022, 2:41am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/4 "2022-11-08T02:41:57Z")
Study this [Thunkable](https://x.thunkable.com/projectPage/62fb85a21668490227ae98f1) i use cloning like crazy in this app without any issues ---
**Author:** ![mimostel](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/mimostel/32/107661_2.png) [@mimostel](https://community.thunkable.com/u/mimostel)\ **Post date:** [November 8, 2022, 6:00am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/5 "2022-11-08T06:00:12Z")
Encountered such thing by myself, and putting some wait 0.001 block right after all label’s texts set fixed the issue (I guess that they need some break time to refresh display new values 🤔) ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [November 8, 2022, 6:03am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/6 "2022-11-08T06:03:36Z")
Thanks for the tip but that didn’t seem to help in my project. ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [November 8, 2022, 6:23am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/7 "2022-11-08T06:23:34Z")
I appreciate that! Your blocks look like mine so I’m still not sure what the issue is. I duplicated the clone source and it’s still behaving oddly. ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 8, 2022, 10:56am UTC](https://community.thunkable.com/t/help-with-cloning/2119681/8 "2022-11-08T10:56:53Z")
> [@mimostel](#): > > me wait 0.001 block right after all label’s texts set fixed the issue (I guess that they need some break time to refresh display new values 🤔) if you wanna share your project via dm I can take a look. There _should_ be no issue with cloning in a layout from what I can tell ---
**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\ **Post date:** [November 8, 2022, 8:14pm UTC](https://community.thunkable.com/t/help-with-cloning/2119681/9 "2022-11-08T20:14:20Z")
I’m going to chalk this up to a corrupt layout or container. I checked and double-checked all of the properties and even though it’s _getting_ the correct values from Firebase, it won’t populate the labels correctly. I started over and created the containers and labels again and it’s working fine. I don’t know what happened but I’ll mark this as solved! ---
**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\ **Post date:** [February 6, 2023, 8:14pm UTC](https://community.thunkable.com/t/help-with-cloning/2119681/10 "2023-02-06T20:14:59Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.