Page Comparison

Use this event to

Description

Add translated labels you can use from your code (i.e. error messages, field names and information).

Messages you add from this event are inserted into "Mobile Messages" and can be accessed from your custom code using the codeunit MobWmsLanguage.GetMessage('LabelName') function.

You may also overwrite existing messages:

• Overwrite Mobile WMS Messages that already exists in Mobile Messages table
• Overwrite labels used in the Android App Mobile Configuration FileFiles (used as "@{LabelName}"). Adding a new message "LabelName" (without '@' or '{}') will overrule messages similar labels from Android App resource files.

Requirements

"Mobile Language Code" must be present filled in on the "Mobile User" Mobile Users (2/10)

Your new eventsubscriber is executed when:

1. ... you manually select the action "Create Messages" from "Mobile Language

...

1. (7/10) -page with this event subscriber active
2. ... a mobile user logs into the database and no "Mobile Messages" exists (usually only the first time a mobile user logs on)
3. ... the Mobile WMS

...

1. extension is upgraded

...

To ensure your new messages is always added to an existing Mobile Wms installation, consider (also) adding the messages from your own Install-/Upgrade-codeunits in your customization app project instead.

Template

    procedure OnAddMessages(_LanguageCode: Code[10]; var _Messages: Record "MOB Message")
    begin
    end;

Example

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Language", 'OnAddMessages', '', true, true)]
    procedure MyOnAddMessages(_LanguageCode: Code[10]; var _Messages: Record "MOB Message")
    begin
        if _LanguageCode = 'ENU' then begin
            _Messages.Create('ENU', 'TESTCODE', 'My custom test translation');
            _Messages.Create('ENU', 'TESTCODE2', 'My custom test translation 2');
            _Messages.Create('ENU', 'SENDER', 'My replaced standard translation SENDER');
        end;
    end;

See also:

Version History

...