Skip to main content

Hello everyone, 

I have a task which needs to be able to update multiple rows in succession, in this case, the pop up for each row is the best option that gives the most readable code. Seeming in this screen, no large chunks of data needs to be processed at once. But I ran in a problem: when I select multiple rows and and this execute this task, it only updates one row. This task only contains one field to make sure we target the correct row in the database. Normally it is hidden, but I set it to read only to see how it would behave. 

This is how the task is set up:
 

Await result was set to Yes (no progress bar) after this screenshot was taken

When I execute the task in the situation intended for our end users, it behaves like the following:

I select multiple rows on which I want to set the slider to the off positon via the task. But instead of updating multiple rows in succession, it only updates one row at a time, the first one I selected during that multiselect.

When I set the field which is hidden for the eventual user to read-only for testing purposes it looks like the following:
 

Here it seems to select the first selected row multiple times. To be specific: the amount times it selects that row is equal to the amount of rows you have selected. 

So my question is: am I missing something, or am I doing something wrong here? I don't think it is supposed to select only one row when you choose the ‘Popup for each row’ option.

@SanderAdam You’re 2nd situation when the field is set to “read-only” does not have anything to show, so I am not entirely sure what happens here.

Do you by any chance have your PK set to include data that changes? The first column that has the order number, does get updated after one activation, so a new records gets the “1” which might be the cause the update seemingly only updates one record, but actually cannot find the new PK of the remaining records?

Another remark, the “Popup for each row” only applies when there are visible parameters. When hidden it will not cause popups to appear. (Maybe the screenshot is not applicable for the hidden situation)

@Mark_Plaggenborg I expect it to update all records selected. The number before the name of the textual name is a number for sorting. It is in no way a primary key. As it is nullable. The primary key, in this case, is the textual value.

And when I set it to hidden, it should update all four records without showing me anyting. Because I thought it was not functional I set the field to read only for debugging purposes. When I did that, it only selects the first selected record four times (if I have four records selected), not the values of all selected rows in succession (and that is what I expect).

@SanderAdam Thanks for adding the 2nd situation. That seems weird behaviour indeed. Hopefully a Thinkwise member can perhaps answer this in relation to how the Universal GUI handles multiple selected rows.

Multi select should absolutely work with your intend as we have similar cases in use, so perhaps it is related to specific settings.

@SanderAdam This is unexpected behavior. Could you please raise a ticket in TCP and include a combination of a recording and the related HAR file?

Reply


Terms & ConditionsCookie settings