Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Description

Examples of sorting Order list.




Sorting on Existing fields

Use OnAfterSetCurrentKey-events.


Sorting on Custom fields

Use.OnAfterSetFrom-events.



Helper Functions

The event parameter "_BaseOrderLineElementView" includes five sorting functions you can use to sort on up to four new custom fields .




Example

[EventSubscriber(ObjectType::CodeunitCodeunit::"MOB WMS Receive", 'OnGetReceiveOrders_OnAfterSetCurrentKey''', true, true)]
procedure OnGetReceiveOrders_OnAfterSetCurrentKey(var _BaseOrderElementView: Record "MOB Ns BaseDataModel Element")
begin
     _BaseOrderElementView.SetCurrentKey(BackendID);
     _BaseOrderElementView.Ascending(true);
end;




Sorting on multiple source

All  except "Ship" have multiple document sources.

I.e. the default sorting for Receive orders list at the mobile device is:

  • First, Warehouse Receipts
  • Then Purchase Orders
  • Then Transfer Orders
  • Then Sales Return Orders

... so essentially "grouping" orders by the four document sources that can all be in the same list (with each "group" being internally ordered by document numbers).

When working with custom sorting, you will need to consider whether orders should still be "grouped" or can now be mixed across the four document sources.



TODO – Keywords:

OnAfterSetCurrentKey:

  • On for fields in table (explain table)
  • Ascending or descending sort
  • Requires table extension to sort on new custom tags, otherwise use Set-functions.
  • Currently do not support retaining "grouping" by document sources

Using Set-functions:

  • For any fields, including new custom fields
  • Can retain "grouping" by document source if desired
  • Cannot set ascending/descending sorting. Must use OnAfterSetCurrentKey for this,



  • No labels