#storeValue not working correctly

1 messages · Page 1 of 1 (latest)

fallen beacon
#

The storeValue function doesnt seem to be working correctly.

I selected a table row which took me to the required page and stored the value as expected. When I then went back and selected a different row, the stored value was not updated.
Then, I added a JS fucjtion to the back button to set the stored value to undefined but that also had no effect, when I went back to the page, all of the previous details were still showing

lucid tundraBOT
#

Hey There,

We've registered your query, and our team will get back to you soon.

Regards,
Pranav

fallen beacon
#

@lucid tundra I have checked all of my apps and every table on every app has the same problem

tawny hollow
#

@fallen beacon thank you for reporting this. I've notified the team and we're investigating.

fallen beacon
#

@lucid tundra the problem seems to have appeared from nowhere... It was working fine a few hours ago and then all of a sudden started to fail. It was one of my employees who brought it to my attention and when I started to investigate i noticed that this issue was not isolated to just one page or one app.
My full install is effected with the same issue

#

@tawny hollow is this a know issue? or is it unique to me?

tawny hollow
#

I don't think it's a known issue yet, but I confirmed the issue in one of my apps after seeing your post. And I think I saw a similar issue with another user. I'll get someone on this ASAP. Sorry for the inconvenience. I'll update here as soon as I have more info.

fallen beacon
#

Thanks @tawny hollow as it stands my apps are currently useless, I cannot use them and I need access to update the companies jobs etc

tawny hollow
#

Understood. I've got someone looking into it already. As a workaround, I noticed that the stored value seemed to be working when set by a button that's directly on the canvas. I think the issue is related to the trigger coming from a table row or button inside a containter/tab. Try adding a button to the canvas that stores the same value from the table's selectedRow, instead of using the onRowSelected action.

fallen beacon
#

@tawny hollow Im not sure I understand fully. How would I do this?

tawny hollow
#

Add a new button directly on the canvas (not in a container/tab) and store the same value that the table row selection was storing. I'm not sure if it will work, but on my end it seems to make a difference if the trigger is inside or outside of a container/tab.

fallen beacon
#

@tawny hollow it seems to be working at the minute. I am finding that it works for a bit then stops working, then after a while starts working again... it is strange

fresh pulsar
#

@fallen beacon Could you please check if you are seeing this issue in the deployed version of your application ?

fallen beacon
#

@fresh pulsar @lucid tundra it is in the deployed version of the app that I first noticed the issue

fallen beacon
#

@fresh pulsar @lucid tundra I have noticed that I seem to be able to use the app as normal, but there is one table that then causes the issue...
The table in the video is the one causing the problems
If i clear cache etc, the rest of the tables work fine, but then, when I access that table, it then causes the same issues on the rest of the tables

fallen beacon
#

@tawny hollow @lucid tundra @fresh pulsar is there any updates on this issue?
my day has been at a virtual stand still as a result.

fresh pulsar
#

@fallen beacon In the back button, instead of setting storeValue('custinv', undefined), could you try removeValue('custinv') ?

fallen beacon
fresh pulsar
#

How about storeValue('custinv', {}) ?

fallen beacon
#

@tawny hollow @lucid tundra @fresh pulsar I added console.log(appsmith.store.custinv) and the log is showing that the stored values are correct in regards to the row that I have selected.
There seems to be something stopping them being transferred to the page

tawny hollow
#

Thanks @fallen beacon . I think the team has identified the issue. I'll update here again as soon as we have an ETA on the fix.

Did the workaround suggested above work for you, or are you still blocked by this?

fallen beacon
#

@tawny hollow nothing has worked yet

lucid tundraBOT
#

Hey Paul,

We're actively working on a fix for this on high priority, and will keep this
thread updated.

fallen beacon
#

thanks @lucid tundra

fallen beacon
#

@fresh pulsar done a screen share and managed to diagnose the problem. I had a post open here #1090978775619096676 message... it turns out that the date needed a .format() at the end. that sorted the problem here and in the link.
There does seem to be an underlying issue somewhere though as, not having .format() seemed to render my full app useless and cause more issues than it really should have.

Sorted now though, thanks for your time and help

Discord

Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.

lucid tundraBOT
#

I'm happy your issue is resolved now.