The existsInvoiceJournal method on TMSFreightBillDetail table causes an unnecessary performance impact due to the size of the records returned. This method is only checking for an existence but returns 80 columns of data

The same method has been used in below areas, causing performance issues, The existsInvoiceJournal method on TMSFreightBillDetail table causes an unnecessary performance impact due to the size of the records returned. This method is only checking for an existence but returns 80 columns of data. Making the attached code change reduced our DB time from 200ms to 20ms.

\Forms\TMSFreightBillDetail\Data Sources\TMSFreightBillDetail\Methods\active 7 53
\Forms\TMSInvoiceTable\Methods\toggleObjects 9 53
\Forms\TMSRouteWorkbench\Data Sources\TMSRoute\Methods\active 14 53
\Forms\WHSLoadPlanningListPage\Data Sources\WHSLoadTable\Methods\active 38 53
\Forms\WHSLoadPlanningWorkbench\Data Sources\WHSLoadTable\Methods\active 30 53
\Forms\WHSLoadTable\Data Sources\WHSLoadTable\Methods\active 42 53