# Regarding Glide caching with a javascript column

**URL:** <https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099>\
**Category:** Ask for Help\
**Created:** [November 21, 2024, 11:47am UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099 "2024-11-21T11:47:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattGlides](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@MattGlides](https://community.glideapps.com/u/MattGlides)\
**Post date:** [November 21, 2024, 11:47am UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099/1 "2024-11-21T11:47:35Z")

</div>

I’ve posted before about caching issues with json objects in columns/querying json in columns and therefore I use these functions in the actual actions(workflows?), I know Glide is aware of this issue.

My question is if the same pertains to javascript columns regarding caching, since there is no option (to my knowledge) to run a script in an action? Can’t really risk it caching with the functionality we’ll be using it for.

---

<div class="post-metadata">

**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\
**Post date:** [November 21, 2024, 11:53am UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099/2 "2024-11-21T11:53:27Z")

</div>

It’s pointless to try caching anything in a JavaScript column. Currently, all computed columns are executed on the client side. Even if you attempt to use JavaScript as a cache, it will still run every time the screen is opened, rendering the effort ineffective or, as they say, “It’s useless”.

---

<div class="post-metadata">

**Author:** ![MattGlides](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@MattGlides](https://community.glideapps.com/u/MattGlides)\
**Post date:** [November 21, 2024, 11:58am UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099/3 "2024-11-21T11:58:49Z")

</div>

Okay perfect so in the scenario where a customer uploads a photo to a column and it becomes a glide url \> they then click submit and our javascript column sets a base64 value, we then clear that photo value from the column \> the customer opens up the screen again to upload a brand new photo and the process restarts

There should never ever be an issue of the script pulling in the previous image url?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [November 21, 2024, 12:05pm UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099/4 "2024-11-21T12:05:33Z")

</div>

> [@MattGlides](#):
>
> My question is if the same pertains to javascript columns regarding caching, since there is no option (to my knowledge) to run a script in an action?

I have seen it happen with a JavaScript column, yes. It was reported to Glide some time back, and they acknowledged the bug. I’m not aware if it has been fixed or not.

---

<div class="post-metadata">

**Author:** ![MattGlides](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@MattGlides](https://community.glideapps.com/u/MattGlides)\
**Post date:** [November 21, 2024, 12:06pm UTC](https://community.glideapps.com/t/regarding-glide-caching-with-a-javascript-column/78099/5 "2024-11-21T12:06:11Z")

</div>

Thank you, will do it externally for now then.