Modern UI grid with action button to print report doesn't update the .Current row

Hi ​@Django In this case you can change your action declaration from your Header DAC to your Detail DAC.

public PXAction<NLABCBulkDetail> PrintSerialReport; 

ensure the currently selected detail line is passed to the server.

I hope it helps!

Are the master-detail grids working correctly otherwise?

Hi ​@Django,

I believe you are missing @columnConfig for the required columns in the grid. You should add those in your .ts file. You can refer to existing SO301000.ts. You can also set grid preset to Details.

preset: GridPreset.Details

You can try using Details.Cache to get the current instead of directly using Details.Current

Hopefully this resolves your issue.

Hi ​@Django. syncPosition: true isn't enough on its own. In Modern UI the grid's selected row only gets sent back to the server if the action is invoked from that grid. Your button sits at the form level, so the round trip only carries the header position and Details.Current ends up null.

Two things you can do:

Move the button into the grid toolbar, that's what gets the row position posted:

@gridConfig({
    syncPosition: true,
    allowInsert: false,
    showFastFilter: GridFastFilterVisibility.False,
    preset: GridPreset.ReadOnly,
    actionsConfig: {
        printSerialReport: { displayOnGrid: GridActionShowMode.Always }
    }
})

And/or stop relying on .Current , pull the row off the adapter instead:

var line = adapter.Get<NLABCBulkDetail>().FirstOrDefault() ?? Details.Current;
if (line == null)
    throw new PXException("Select a pallet line first.");

For that to work well, declare the action against the detail DAC (PXAction<NLABCBulkDetail>) so the adapter builds from the Details view.

I'd do both honestly, the toolbar move fixes the UX, and the adapter check keeps you from hitting a null ref when nobody's selected a row.

​

Yes. When I click on the master grid, the detail grid filters appropriately. As I change the selected master grid row, my graph RowSelected code is run.

However, when I change the selected row in my Detail grid, the related RowSelected code is not run.

The Detail grid RowSelected code is run when I’m editing the field in the grid and when I change the master grid record ( runs multiple times as expected).

​@Abhishek Niikam I switched the DAC that the action button is working on to both the master level as well as the detail level but I get the same result. The Current record for the detail grid is the first record in the grid no matter what line on the grid the user has selected.

​@dnavasardyan37 Unfortunately, the adapter parameter contains almost no information at all and the Cache is always pointing to the first record in the detail DAC and not the record that the user has selected.

Perhaps the issue is related to the detail grid being within a splitter. I’m going to try removing that to see if it makes a difference.

Very frustrating given that Classic UI works perfectly for all of this.

​

​@Django 
If it working in Classic view, it means backend(graph) side ok there is no problem I guess.
I hope problem with either html or ts

make sure below code in html & ts

here is the sample code which I was using for action button in one of the screen in my project

html
 <qp-button id="TestConnection" state.bind="TestConnectionAction"></qp-button>

ts

TestConnection: PXActionState;

Important!. PXActionState