In an earlier version of our app a SetParams function for a table has been written.
In this function a list is created where every item consists of a dictionary with all the items of the table.
The items were not in the same order als the table, but based on the name of the parameter matching the name of the column, every parameter ended up in the right column
Since the app is updated to a later version (not necessary only since the current version), all the parameters are messed up (in the wrong column) after using the SetParams function. It seems in this version, the name of a dictionary item does not matter anymore, only the order of the items in the dictionary determines where the parameter is written to in the table
I would expected to not be surprised by this bug, but to have a notification or a warning or something about the new way this works in Viktor. If this notification has been there, I’ve missed it.
Notifying you about this misunderstanding, for you to learn from.
Developers within VolkerWessels are losing trust in Viktor (if only a bit) when surprised by things like this.