Profound Logic Forums

I'm have an issue processing all the rows I select in a sub-file.

Condition:
I've created an app with 2 active sub-files.
I want to select multiple rows from one sub-file and assign them to the second sub-file.

Process:
When I select a row from the sub-file and click the slide bar and drag it down in the sub-file and press and hold the shift key then click another row then all the rows between are selected.
Lets say I've selected one thousand rows.
I then click the assign button to assign those selected rows to the second sub-file.

Results:
The program will only assign about 150 of the 1000 rows to the second sub-file.
It looks like the READC op code is not reading all 1000 records selected.
But if I click under the slide bar several times to move down the sub-file and select 1000 rows they seem to all get processed when I click the assign button.

Can you help me solve the above condition?
Thanks.

Tony,

I would like to debug this on my system. Could you please get a JSON dump of the screen in question and email it to support?

To get the JSON file, do the following:

1. Navigate to the screen in question.
2. go to the browser's address bar and enter javascript:pui.downloadJSON()
3. Press enter and save the file that downloads.
4. Email this text file to support

Here is the json.txt file you requested

I posted the JSON.txt file to this message thread.
Do you have any idea why this select does not work?

I will attach a copy of the screen and program source.

I've had a look at the JSON dump and can see the problem. It appears to be a bug. The UI framework is not marking all the records as "changed", nor is it setting the selection field value in all records.

This is why when you READC, you are not getting them all.

I've reported to the develoment team for a fix, using your example. Will advise when a patch/update is available to correct the problem.

Since the problem seems to relate to scrolling in the subfile, probably the only workaround is to page the list (so there is no scrollbar) until a fix can be made.

Looking at how this application is used, though, I can understand how that's not a very good workaround. We'll try to correct as soon as possible.

Thank you David.

This is fixed in current release, 4.0.3.

Thank you David.