In NAV 2013 you need to set a secondary key on the Transfer Shipment Header table and then use SETCURRENTKEY. In versions earlier than Dynamics NAV 2016, if a Dynamics NAV key that started with the fields that you specified as parameters to SetCurrentKey did not exist, then you received an error when you called the SetCurrentKey function. This provided a degree of protection in versions earlier than Dynamics NAV 2016 against accidentally requesting a sorting for which no index existed. In Microsoft Dynamics NAV 2018, an index is not required to support a certain sorting, but sorting without an index could lead to bad performance if a search returns a large result set, which would then have to be sorted before the first row is returned.
↧