Cannot get a custom action to show on grid toolbar in MUI

Hi Joe,

Have you tried adding ChangeLocationID: PXActionState; inside LocationDetail from the path:

src/screens/CR/common/tabs/tab-locations/tab-locations

This should make your action appear in the Locations grid.

I think you need to import AR303000_Locations from  ../AR303000_Locations and extend that rather than ‘Location’.

Hi ​@darylbowman   I did try that.  If I publish this, it tells me I have a duplicate key and I literally have to delete the site and reinstall it.

This is the import I was using:

import { AR303000_Locations } from "src/screens/AR/AR303000/Extensions/AR303000_Locations";
 

I am afraid to publish this as it will take another hour to delete the site, reinstall it and get everything back to working

import {
    PXFieldState,
    PXView,
    viewInfo,
    createSingle,
    gridConfig,
    PXActionState,
} from "client-controls";
import { AR303000 } from "src/screens/AR/AR303000/AR303000";
import { AR303000_Locations } from "src/screens/AR/AR303000/Extensions/AR303000_Locations";
export interface AR303000_AgroShip_converted extends AR303000 { }

//action that is showing on the main toolbar.
export class AR303000_AgroShip_converted {
    @viewInfo({ containerName: "Change Location ID" })
    ICSChangeLocationIDValueView = createSingle(ICSChangeLocationIDValue);
}

//Attempt to add the button to the grid
export interface AR303000_Location_AgroShip_converted extends AR303000_Locations { }
export class AR303000_Location_AgroShip_converted {
    ChangeLocationID: PXActionState;
}
@gridConfig({
    topBarItems: {
        AddNew: { index: 0, config: { commandName: "ChangeLocationID", text: "Change Location ID" } }
    }
})

//Adds the field to the popup
export class ICSChangeLocationIDValue extends PXView {
    UsrNewLocationID: PXFieldState;
}

Before I publish this, do you think my import reference is bad?  I don’t know of any other way to get it to compile.

publishing now.  Hopefully I don’t kill my site.

Killed my site.  Re-installing.

You shouldn’t need to reinstall. Just change the code back and build again?

The project wont publish.

I close the publish window and I get this:

I can find no way to remove whatever is causing this error.  Time to reinstall.

I strongly recommend not publishing my ts code, or you will regret it.

I uploaded the project if you want to look at the code.  DON’T publish it!

Just edit the file in the Modern UI files section and then republish.

Ideally, you’d build the files locally before adding them to the package. There are quirks and once any MUI files are published, the locally built files no longer work, but it will save you hordes of time republishing.

I cannot republish.  You cannot even open the site to get to the publish anything.

I do all my ts file editing in VS, then check for updated MUI files in the project editor.

Sorry if I’m not explaining this correctly.

But you still need to republish each time, right? Using npm, you can ‘build’ (compile) the TypeScript into the JavaScript files Acumatica uses without publishing. It’s much faster than having to publish each time.

I will give the npm option a try.   

For what it’s worth, when I tried my original code, I got the same error, but because I was building with npm instead of the publishing UI, I simply edited the code file, rebuilt, and refreshed the page.

I get a red squiggle

Sorry for all the questions

Try this: 

import { AR303000_LocationDetail } from "src/screens/AR/AR303000/extensions/AR303000_Locations"

​@darylbowman your last two posts got it working.  

I split the location extension into a separate file.  Maybe trying to put both the popup extension and the location extension caused the catastrophe.