I have gone looking around and I have not seen this method before so I thought I would share it.
If you are like me/us then you hate the landing pages with a passion but disabling them the way that support used to suggest by overriding the Form_OnLoad and pointing it to Main does not allow (at least in my experience) the ability to multi-select search from the screen, you must go back to the landing page and search from there. Likewise the ‘breadcrumb’ menu was broken when I tried doing it this way.
Instead I dug into what they were doing with the Part screen as that screen functions properly. I am not sure what versions have this flag but in 2024.1.8 at least it exists, the “TransView.SysBypassLandingPage” is how Epicor seems to be doing this with Part (this flag changes a number of event logic and is the key from what I have found).
The way I have been able to do this is to duplicate the “SysInitTransView” event and put in the trigger to override it. Then in the row update, column 9 of the update references this flag, changing the value from false to true effectively eliminates the landing page, maintains multi-select search from the normal screen and the breadcrumb menu.
I did have some really weird results doing this with customizations that were uplifted from classic but in from scratch layers it seems to work fine, having deployed it to Quote, Order and Job so far I am continuing down the list until all traces of the landing page disaster have been removed.
I have seen others discuss the possibility of having it be flagged as a choice and I am sure you could put in a message or some such with conditions to drive it but I have not, and will not look into that as we do not even want it to be an option for the user.