Force selection of first record on query result.

KnightWare

The the "Select First Record" is checked on a query, and works when the query initiates and runs on a presentation panel. However further Auto-refreshes (such as Process run, or other BO changed) refreshes the query but does NOT select the first record. Anyway to force this?

PointsWell

https://awareim.com/forum/https://www.awareim.com/forum/d/11633/6&hilit=First+record+refresh#p53840

KnightWare

Looks interesting, but not for me it's not a child/parent relationship. When I added that JS to the render script of the query, the Auto Refresh stopped working.

I have query results (grid) on one panel of my presentation. As described in your link, first record highlight's and selects when first presented. However when another BO on another panel is modified, the query is set to auto refresh, which it does. Just the first record does not highlight and get selected. I need the selection to trigger after the refresh, so a process runs to to set the other objects in the presentation.

I figured I need to instantiate the grid object as your javascript does, but not familiar with the syntax.

PointsWell

The linked solution works in the way you are asking, an update elsewhere triggering a refresh in the target grid and the target grid not doing the select first record.

KnightWare

I placed the code as is in the Render Script of the Query. When I did, the Query did NOT refresh when the other BO was saved. ,

PointsWell

KnightWare wrote
I placed the code as is in the Render Script of the Query. When I did, the Query did NOT refresh when the other BO was saved. ,

Hmm that worked in, I think, v8.4, I wonder if the Kendo update affected this.

johntalbott

Are there errors in the browser console?

A quick screencast demonstrating the problem would help a lot.

KnightWare

No errors reported in Console. Having this code in the render script of the Query defiantly stops the auto refresh.

widget.bind("dataBound", function(e){
const grid = e.sender;
grid.select("tr:eq(0)");
grid.select().click();
})

Remove it and the grid refreshes , but first row not selected.
Screencast?

KnightWare

johntalbott - sent you PM

Jaymer

KnightWare wrote
No errors reported in Console. Having this code in the render script of the Query defiantly stops the auto refresh.

yes, i agree

added this code, and even clicking the refresh icon would NOT redraw the grid. A process had added a record and it would not show up. Before adding this code, the built-in aware refresh mechanism was updating the grid after my process added a record.
I'm trying to get that new, top-most record selected, so it will fire the default Row Operation.

Had to refresh (re-login) the entire app to make that panel redraw to show the new record.

Jaymer

this is a visual example of whats happening from the original post:

1st pic shows parent-child grids.
top one has 'select first record'
default actions runs process, saves an ID, DISPLAYs the child query

another panel (not shown) has a button to add a new transaction, via process.
2nd picture shows AFTER the top grid auto refreshed based on that process running. this is correct behavior.

NOTE how the "first record" DID NOT get selected on the refresh, leaving the user to manually click on the new record to show the correct child.
The selected record (in brown) stayed selected, and moved from top to the 2nd spot as the new one came to the top.

johntalbott

Try this ...

widget.bind("dataBound", function (e) {
    const grid = e.sender;
    const row = grid.table.find("tr:eq(0)");
    

parser.highlightRow(row, grid); // This is what highlights (selects) the row.
grid.select().click();  // This is only needed to run the default row operation.
})

KnightWare

JohnTalbott - That put it in an endless loop. Placing it in the render script of the query. Need to dig in because that doesn't make sense to me.

Jaymer

I agree - endless loop - no good

johntalbott

It works for me. Show me the endless loop.

johntalbott

Make sure "Select first record" is unchecked.

KnightWare

John Talbott
https://www.dropbox.com/s/q19g14cuzuilwsd/AwareImGridLoop.mp4?dl=0

PointsWell

Vlad gave me a fix for the endless loop. Let me look for it

johntalbott

Just to be sure ... this is with "Select first record" unchecked?

What happens if you remove this line?

grid.select().click();

PointsWell

Found the conversation with Vlad - note it requires you to use Processes as default operations rather than the built in operations.

I did not test it. Other priorities.

Would be nice to have a built in fix to consistently select the first record even with a refresh. Or be able to have queries listen to other queries rather than be driven by them,

Hi,

have you tried disabling auto-refresh of the process which runs as a default operation on the ShowChildren query?

(when you define an operation that starts a process there is a "No Auto-refresh" checkbox. Try ticking it.)

Best Regards,
Vladimir Simkin

Hi Vlad

I’ve discovered a situation that will generate an accidental infinite loop. I have created a sample BO for you which demonstrates this. This reflects what is happening on my system in a simplified way. This set up is due to the 1:1 Push operations of panels and the inability to m:1 Pull data from a source

Setup:

BOs
Parent
Child

Queries
All Parents - has default action SelectParent (see below)
ShowChildren of selected Parent - FIND Child where Child.obParent.ID=LIRU.IDParent, this query is set to auto refresh on the running of the Parents default Operation on Record (below) - ShowChildren has Select First Record set

Operations on Records
SelectParent - Set LIRU.IDParent - this runs on the All Parents view as a default action. It sets the LIRU.IDParent to the ID number of the Parent record.
ChildShowParent - default operation on record on query ShowChildren to start a process which just does VIEW Child.obParent USING a specified form.

ShowChildren query also has a render script on it
widget.bind("dataBound", function(e){
const grid = e.sender;
grid.select("tr:eq(0)");
grid.select().click();
})

The render script is required because the select first record is not respected when the grid refreshes following running of the SelectParent process.

If you just use View Object as the default operation then the issue doesn’t occur, BUT because I want to show the parent object of the Child (in order to show the multiple children of the Parent) I have to use an Process kicked off by the default action of the Query to VIEW Child.obParent USING ChildParent

This creates a situation where the Process runs, which is causing an unwanted refresh on the ShowChildren query, which causes the default action to kick off, which causes an unwanted refresh ad infinitum.

In the sample attached run it in test, it will open to the Administrator VP. The Admin VP has two tabs, select the tab Test, the Parent Record will be selected, which will cause the ShowChildren grid to refresh and then the loop will start. I have made the Test tab closable otherwise it locks me out of my single user dev environment.