# Stored Variable return Null instead of text

**URL:** <https://community.thunkable.com/t/stored-variable-return-null-instead-of-text/2200274>\
**Category:** Questions about Thunkable X\
**Created:** [December 31, 2022, 6:35pm UTC](https://community.thunkable.com/t/stored-variable-return-null-instead-of-text/2200274 "2022-12-31T18:35:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 2, 2023, 3:48am UTC](https://community.thunkable.com/t/stored-variable-return-null-instead-of-text/2200274/4 "2023-01-02T03:48:12Z")

</div>

@conroy33 What would be the best way for users to suggest additions to the documentation pages? There are lots of little nuggets of wisdom like this that are hidden in forum topics but could be added to the documentation. For example:

> [@\[Solved\] "Does List Contains" does not work](https://community.thunkable.com/t/solved-does-list-contains-does-not-work/2190935/2):
>
> Don’t use the [gear] list block. It creates a list. So when you have [gear] list [list of items] you’re creating a list of a list and it won’t work with the does contain block. You don’t need to tell Thunkable that the [list of items] block is a list… it already is.

And the way to use text strings in cloud variables to reference Firebase key:value pairs.

---

_[View the full topic](https://community.thunkable.com/t/stored-variable-return-null-instead-of-text/2200274)._
