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.
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”.
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?
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.
Thank you, will do it externally for now then.