Skip to main content
12-Amethyst
January 12, 2026
Solved

DistributionTarget Table right click on row

  • January 12, 2026
  • 1 reply
  • 43 views

Remove action on table header is pointing to our custom class, similarly i want the remove action on right-click of a row also to point to the same class. 

11025060_1-1768233751984.png

 

 

Best answer by TDT

Hi @11025060,

 

The disassociateDistributionTarget action is the same action used in two different models: the distributionHistory table toolbar actions and the distribution table nmActions.

 

In the screenshot you shared, it is indicated that the disassociateDistributionTarget action in the distributionHistory table toolbar is hidden by a filter. However, in OOTB behavior, this action is validated by AssociateDistributionTargetsActionValidator, not by a filter.

 

If a filter has been implemented in your system, it does not appear to be the correct approach. The recommended implementation is to extend AssociateDistributionTargetsActionValidator with a custom validator. Using a filter effectively bypasses the OOTB validator logic and replaces it with custom filtering. However, it is possible that the developer who implemented this solution may have reimplemented the OOTB validator logic within the custom filter.

 

I have registered the validator on the disassociateDistributionTarget action, and the validator is being triggered correctly both at the table toolbar level and at the object row level.

 

TDT_0-1768406775852.pngTDT_1-1768406821895.png

 

 

 

1 reply

TDT16-PearlAnswer
16-Pearl
January 14, 2026

Hi @11025060,

 

The disassociateDistributionTarget action is the same action used in two different models: the distributionHistory table toolbar actions and the distribution table nmActions.

 

In the screenshot you shared, it is indicated that the disassociateDistributionTarget action in the distributionHistory table toolbar is hidden by a filter. However, in OOTB behavior, this action is validated by AssociateDistributionTargetsActionValidator, not by a filter.

 

If a filter has been implemented in your system, it does not appear to be the correct approach. The recommended implementation is to extend AssociateDistributionTargetsActionValidator with a custom validator. Using a filter effectively bypasses the OOTB validator logic and replaces it with custom filtering. However, it is possible that the developer who implemented this solution may have reimplemented the OOTB validator logic within the custom filter.

 

I have registered the validator on the disassociateDistributionTarget action, and the validator is being triggered correctly both at the table toolbar level and at the object row level.

 

TDT_0-1768406775852.pngTDT_1-1768406821895.png