Skip to main content
Question

Custom LinkCommand not working in Modern UI (field displayed as text only)

  • May 16, 2026
  • 5 replies
  • 64 views

Forum|alt.badge.img+1

I have an issue with a link not being displayed on a custom field in Modern UI.

#region UsrInvoiceID 
public abstract class usrInvoiceID : BqlInt.Field<usrInvoiceID> { }

[PXDBInt()]
[PXUIField(DisplayName = "Invoice ID", Enabled = false)]
[PXDefault(PersistingCheck = PXPersistingCheck.Nothing)]
public int? UsrInvoiceID { get; set; }
#endregion

I have also implemented a LinkCommand in the graph, and configured the same LinkCommand in the ASPX page.

In Classic UI, everything works correctly — the field is shown as a clickable link and it opens the expected page.

However, in Modern UI, I do not see a link on the field. It is displayed only as plain text.

I also tried adding a selector control to the field. This makes it appear like a link in Modern UI, but clicking it does not navigate to the expected screen.

Is there a different approach or additional configuration needed for this scenario?

5 replies

Forum|alt.badge.img+3

Hello ​@Marat43  You have to add lines in .ts file to expose link in MUI:
e.g.
 

export class YourViewName_Extension {
@linkCommand("YourLinkCommandName")
@columnConfig({ width: 100 })
UsrInvoiceID: PXFieldState<PXFieldOptions.Disabled>;
}

& if it is in grid then try like this:
 

@columnConfig({
editorConfig: {
linkCommand: "YourLinkCommandName"
},
width: 100
})
UsrInvoiceID: PXFieldState<PXFieldOptions.CommitChanges>;


I hope it help!


Forum|alt.badge.img+1
  • Author
  • Semi-Pro I
  • May 19, 2026

@Abhishek Niikam Unfortunately, this did not help.


Forum|alt.badge.img+3

@Marat43 can you share your .ts , .html file code for this field so we can detect issue


Forum|alt.badge.img+1
  • Author
  • Semi-Pro I
  • May 20, 2026

@Abhishek Niikam  Yeah sure,

 

TS:

import {
PO301000,
POOrderHeader
} from "src/screens/PO/PO301000/PO301000";
import {
PXFieldState,
PXFieldOptions,
controlConfig,
linkCommand
} from "client-controls";
export interface PO301000_Custom extends PO301000 { }
export class PO301000_Custom { }
export interface POOrderHeader_Custom extends POOrderHeader { }
export class POOrderHeader_Custom {
UsrCustomStore: PXFieldState<PXFieldOptions.Disabled>;
@controlConfig({ allowEdit: true })
@linkCommand("ViewPO")
UsrCustomPOID: PXFieldState<PXFieldOptions.CommitChanges | PXFieldOptions.Disabled>;
UsrCustomPONumber: PXFieldState<PXFieldOptions.Disabled>;
}

HTML:

<template>
<template modify="#fsColumnC-Order">
<field name="UsrCustomStore"></field>
<field name="UsrCustomPOID"></field>
<field name="UsrCustomPONumber"></field>
</template>
</template>

 


RohitRattan88
Acumatica Moderator
Forum|alt.badge.img+4
  • Acumatica Moderator
  • May 20, 2026

@Marat43,

allowedit works on fieldset for selector controls:

You have defined the links in the selector controls for the CustomerIDServiceID, and DeviceID fields by specifying allowEdit: true in the controlConfig decorator.

Data Entry Form: To Create the UI of a Data Entry Form

linkcommand only works for grid:

The decorator works only for the columns of a grid control.

Function linkCommand

 

I suggest creating proper field declaration(selector) in graph in order to add link to associated document.