# Quick Tip - Keeping App and Stored Variables from breaking when copying from My Screens

**URL:** https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845
**Category:** Questions about Thunkable X
**Tags:** my-screen
**Created:** [December 10, 2020, 11:09am UTC](https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845 "2020-12-10T11:09:19Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![drted](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/drted/32/92694_2.png) [@drted](https://community.thunkable.com/u/drted)
#### Post date: [December 10, 2020, 11:09am UTC](https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845/1 "2020-12-10T11:09:19Z")

</div>

I have a screen template I use that has all sorts of “Helper” function. But every time I add it to a project, all of the app and stored variables break requiring a lot of work to point them to the current project version of those variables. Examples are the stored email address of the currently authenticated user

An easy fix just dawned on me. Rather than use the normal app or stored variable blocks, I specify the variables by a text value.

![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/f/6/f6e8ff70b1dc16c2ca62a7eb3e534b6571732def.png)

---

<div class="post-metadata">

### Author: ![eko.devs.apploroceo](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/eko.devs.apploroceo/32/93147_2.png) [@eko.devs.apploroceo](https://community.thunkable.com/u/eko.devs.apploroceo)
#### Post date: [December 10, 2020, 12:34pm UTC](https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845/2 "2020-12-10T12:34:29Z")

</div>

why dont u make it to  
#guide

---

<div class="post-metadata">

### 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: [December 10, 2020, 5:27pm UTC](https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845/3 "2020-12-10T17:27:25Z")

</div>

Hmm… that seems like a wise workaround. I would think it would **not** break if you also initialized the variables on that same saved screen. Although maybe it then breaks any existing variables on non-saved screens. But your method takes away that requirement anyway… I like it!

---

<div class="post-metadata">

### Author: ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)
#### Post date: [November 8, 2024, 12:19pm UTC](https://community.thunkable.com/t/quick-tip-keeping-app-and-stored-variables-from-breaking-when-copying-from-my-screens/1031845/4 "2024-11-08T12:19:52Z")

</div>