Our order entry is missing the option to close or void line from the Lines card in v. 2025.1. This was useful in v 2022.2.9. ![]()
I have tried to add it in Appl. Studio under Action Data for the Lines “list view”. Has anyone had any luck with this?
If you click on the line to enter line details, can you close the line from the overflow menu? I know its not the solution you asked for, but might be a good workaround in the meantime.
Yes, thanks. They are aware of it on the Details. They are dealing with a large volume and stay on the ‘lines card’ as much as possible.
You can customize to build it back…
First… why is it missing?
Epicor is using a Data Rule to HIDE those tools if you’re not on the OrderDtl page.
So, just add that tool/Data Action back into the Line panel card grid on the main Sales Order page. Easiest way is to copy the settings of the stock tool, and you’re off and running (or one might think). Here is the stock “tool”:
BUT… there is a catch… Notice this stock tool is BOUND to OrderDtl.CloseLineTool
Referring back to the above mentioned Data Rule, the action is hiding anything bound to “OrderDtl.CloseLineTool”. So, if you manually try to add the tool back in and use the same binding… your tool is also going to be invisible.
The key here is to use a different binding… or… none at all!
Now, the data rule won’t hide your custom button.
Then… copy the stock OnClick_toolOrderDtlClose event, and simply change the trigger to onclick of your new tool (so the same Close Line event logic runs).
Test: New tool is visible
Success:
Page refreshes after clicking okay:
Line 2 shows as closed.
Repeat the above for your own “Re-Open Line Tool”.
General Disclaimer… as with any “work around”… there is other logic going on. For example, if you are on the Line Detail page of a line that is already closed, the stock “Close Line” action is greyed out. Can’t close what is already closed.
Because I didn’t bind my new tool/Action and add logic to disable it when the line item is closed… it will allow me to try to close a closed line. It runs through the events again, tells me Line 2 is closed (again) probably not the end of the world. Just be cautious when working around things… could always be other functionality or unthought of repercussions.
Good find David!








