This is the simplest form of interaction with the back-end.

• The user selects the action and the current Order Line information is sent to the back-end.
• No dialog is presented to the user

You can add the action to either an:

• Planned function
• Unplanned function
• Lookup

Adding to a Planned function

Planned functions are Pick, Receive, Put-Away etc.

Which data will be transferred to back-end?

The sendRegistrationData attribute will decide this. The attribute is only valid on Order and Order Line Pages.

• Order: All registrations made on the order will be included in the request sent to the server. This will include order header, order level registrations.

• OrderLine:  then only the registrations for the selected order line (Order line registration and extra information) will be included in the request sent to the server.
  The order tag will be added to the response but only contain information about the selected order line. This is only valid on a Order Line Page.

How to enable for Planned function

Step 1:  Add the action in Configuration file

In  Application.cfg 

"UnableToPick" action is added to the existing “Pick Line” page

<adhocRegistration registrationType="UnableToPick" id="2" icon="postsuccess" title="Unable to Pick" sendRegistrationData="OrderLine"> <onSuccessfulPost refreshOnSuccess="true"/> </adhocRegistration>

Insert here:

Step 2: Test the request 

After restart you can now select the action and inspect the Request it makes.

<request name="PostAdhocRegistration" created="2019-07-30T14:38:18+02:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="PostAdhocRegistration">
    <selectedItemType>OrderLines</selectedItemType>
    <backendId>PI000003</backendId>
    <lineNumber>30000</lineNumber>
    <RegistrationType>UnableToPick</RegistrationType>
    <Order backendID="PI000003" xmlns="http://schemas.taskletfactory.com/MobileWMS/RegistrationData" />
  </requestData>
</request>

Step 3: Add code to handle action in NAV

• The call goes into codeunt “TF Mobile WMS Adhoc Registr.” 
• Function “PostAdhocRegistration()”
• Modify the code to handle this new Registration Type.
  
  

Add to a Lookup 

Lookup's are: Bin Content, Locate Item etc.

Which data will be transferred to back-end?

Only the selected lookup entry will be transferred.

The sendRegistrationDataattribute does not apply to lookup.

How to enable for Lookup

Step 1:  Add the action in Configuration file

In  Application.cfg 

"UnableToPick" action is added to the existing “Pick Line” page

<adhocRegistration registrationType="MyLookupResultAction" id="2" icon="postsuccess" title="My Lookup Result action"> <onSuccessfulPost refreshOnSuccess="true"/> </adhocRegistration>

Insert here:

Step 2: Test the request 

After restart you can now select the action and inspect the Request it makes.

<request name="PostAdhocRegistration" created="2019-12-06T14:08:10+01:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="PostAdhocRegistration">
    <Location>WHITE</Location>
    <Bin>W-01-0003</Bin>
    <selectedItemType>Lookup</selectedItemType>
    <ItemNumber>TF-002</ItemNumber>
    <Barcode />
    <DisplaySerialNumber />
    <SerialNumber />
    <DisplayLotNumber />
    <LotNumber />
    <DisplayExpirationDate />
    <ExpirationDate />
    <Quantity>1</Quantity>
    <UoM>PCS</UoM>
    <DisplayLine1>TF-002</DisplayLine1>
    <DisplayLine2>Intense Orange</DisplayLine2>
    <DisplayLine3 />
    <DisplayLine4>UoM PCS</DisplayLine4>
    <DisplayLine5 />
    <ExtraInfo1 />
    <ExtraInfo2 />
    <ExtraInfo3 />
    <RegistrationType>MyLookupResultAction</RegistrationType>
  </requestData>
</request>

Step 3: Add code to handle action in NAV

• The call goes into codeunt “TF Mobile WMS Adhoc Registr.” 
• Function “PostAdhocRegistration()”
• Modify the code to handle this new Registration Type.