Dear KNIMErs,
I am trying to build an application, where the user should be able to upload a spreadsheet file (xlsx) and once this is done, the should click a button to get an updated list of columns to choose from.
This is my current setup, however, the dropdown in the Value Selection Widget node does not change:
Whenever I choose a new file in the File Upload Widget in the interface, the Value Selection Widget node DOES NOT get updated. And I don’t really understand why.
Thanks in advance for your kind help.
Hi,
I’m not sure if this helps, but have you enabled the “re-execution” options in the widget settings?
1 Like
Thanks a lot for your response @ActionAndi . But as per my understanding, this only executes, if the value in the dropdown is changed. But I want to update the content of the dropdown table BEFORE users select something from it.
I looked at quite a few workflows using the Refresh Button Widget node so I don’t really get, why it’s not working. If it’s execution triggers all downstream nodes to re-execute, basically the Read Excel Sheet Names node should be re-executed and then fill the Value Selection Widget node with the new values, but it doesn’t.
Hey @kowisoft,
I need to check, but my first guess would be, that the assumption of the whole component is that the File Upload Widget refreshes the output if you select a new file. But this is not the case. It only does it as soon as the new value is applied. So this widget itself would need a refresh button before it.
In your case clicking the refresh button will always trigger a re-execute with the same value that was originally pushed to the Read Excel Sheet names, which is also why you don’t see any change.
I think in general it would be a nice idea that the File Upload Widget can trigger a re-execute itself after the file upload is complete.
Greetings,
Daniel
1 Like
ah, that’s a very helpful insight @DanielBog
But if I then put this into 2 different pages (aka 2 different components), then it should be working, also without using the Refresh Button Widget node, right?
Yes, exactly. It should also work if you connect the refresh button to the File Upload widget directly and remove the option to save it to the workflow data area (With this option set it seems to not work. I would guess that some temp folder gets cleared if the widget is reset).
Greetings,
Daniel
2 Likes
hmmm. But this again renders the node useless for my business case. Because why do I need a file upload widget? Exactly to save the uploaded file to a temp storage on the hub. That looks like a bug to me (in case one wants to use the single page approach with the refresh button widget).
Edit:
here’s another example:
I simply do not understand, why this does not update the table at all. The visual logic here clearly says “Once someone presses the button, run everything from the Concatenode onwards”.
What my users do in this example: they enter two new values, out of which a new table row is created. This should get added to the existing table by using the Concatenate node.
But it simply doesn’t do that.
I even connected the Refresh Button Widget node to the Integer and Double Widget nodes. Then the table gets updated but always the same row which is - with all due respect - complete nonsense. Where do I tell it to only update existing rows???
I personally find that this makes the whole handling of this specific node very unintuitive and illogical.
