I am designing an optimisation loop that will allow users to input the data on the web portal. I currently use the table editor node to allow the users to do so. However, I cannot seem to find a flow variable on the configuration to reset the table every time. It currently contains the data from the previous use which is not something I want. Just wondering if anyone has any advice/ideas on how to get round this issue.
does your table contains missing/empty values at the beginning and by reset you mean to go back to that state? Can you shows us or at least describe your workflow design a bit more?
I can’t really share the workflow here but I will try describe it a bit better. We are designing a interface for our users to apply optimisation loops to their data. So depending on the user there will be a different data set. So due to this I want the table editor to reset after every use and not store the previous values selected as this could lead to issue and obviously the missing value would make it clear to the user that a value needs to be inputted.
but what kind of loop are you using? Parameter Optimization Loop Start/End or something else? And you are talking about multiple users but I assume Table Editor needs to be reset between different loop iterations as different users will start different jobs and at beginning they should have clean Table Editor?
There is no need to share workflow, some pictures should be sufficient
Hi @meldruc , can you please explain what the solution was so that other users from the community can learn from it if they ever have the same question?
Hi, yes no problem. My workflow requires user to make selections via the interactive display through components by the web portal we have. On the first interactive page the user will make a selection based on which data set the wish to analyse.
The table editor node will retain the values stored by the user when it is executed (from what I gather there is no automatic way currently to reset the table editor node). But table editor will effectively reset if there is a different data set which works in my case as the users have specific assigned data sets they will look at. So the only time it will not reset is if the workflow is run for the exact same data set which does not cause too much of an issue as the range for the optimisation should be in suitable range.