Pack & Ship Extension - OnDiscoverShippingProvider (MOS)

(Legacy) OnPrem/Per-Tenant Extension

This article was written for a connector used with the separate Pack & Ship Extension (OnPrem or Per-Tenant).
Pack & Ship is now a feature in the standard Mobile WMS (since MOB5.42) and will use a new API to connect directly to the Mobile WMS App.

Existing custom connectors can be migrated by following the guide How-to: Migration of Pack & Ship.

Links:

Mobile WMS - Implementing a new Shipping Provider Connector
Mobile WMS - Read Master Data from 3rd party Shipping App

Use this event to

Expose your custom ShippingProvider Connector App to Tasklet Pack and Ship Extension.

Description

Each 3rd party Shipping App being integrated into "Tasklet Pack and Ship" must provide a unique "Shipping Provider Id" identifying this exact "ShippingProvider" Connector App integration.

The "Shipping Provider Id" is used to separate imported master data from various 3rd party Shipping Apps that may otherwise use conflicting codes (i.e. two implementations both using Package Type = 'BOX').
Tasklet are using Id "SHIPIT365" for the out-of-the-box ShippingProvider implementation for "IDYN ShipIt 365".

Template

[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOS Pack API", 'OnDiscoverShippingProvider', '', true, true)]
local procedure OnDiscoverShippingProvider()
begin
end;

Example

[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOS Pack API", 'OnDiscoverShippingProvider', '', true, true)]
    local procedure OnDiscoverShippingProvider()
    var
        MosPackAPI: Codeunit "MOS Pack API";
    begin
        MosPackAPI.SetupShippingProvider(GetShippingProviderId(), 'My custom ShippingProvider Connector App');
    end;

local procedure GetShippingProviderId(): Code[20]
    begin
        exit('MYSHIPPINGPROVIDERID');
    end;

Version History

Version	Changes
MOS1.0.0	Introduced