To-dos in Microsoft Dynamics NAV are shown as activities in Mobile Sales. In Microsoft Dynamics NAV, a to-do often contains several activities, but in Mobile Sales an activity exists independently of other activities, and a to-do displays as an activity. In order for Mobile Sales to use a to-do from Microsoft Dynamics NAV, the to-do must meet the following requirements:

• The to-do must be of type Meeting.

• The to-do must be assigned to a salesperson.

• The to-do must be for a single contact of type Company.

• The to-do cannot be an all day event.

• The to-do cannot be canceled.

You can set Microsoft Dynamics NAV to automatically send all of the to-dos that meet these requirements to the Mobile Sales Activities table. Mobile Sales can then synchronize the table with the mobile devices. To set Microsoft Dynamics NAV to send to-dos to the Mobile Sales Activity table, you must specify this in the Mobile Sales Setup window. This will send all future to-dos to the table. For more information, see How to: Enable Mobile Sales Activities in Microsoft Dynamics NAV Classic.

To send all existing to-dos to the Mobile Sales Activity table, you can run the Mobile Sync. To-do/Activity batch job. You can also run this report if the To-do table and the Mobile Sales Activity table are not currently synchronized. Alternatively, you can create a job queue entry to run the batch job at regular intervals.

Note
You must choose to either schedule the Mobile Sync. To-do/Activity batch job to run in the job queue, or set Microsoft Dynamics NAV to send new to-dos automatically as part of the Mobile Sales setup. However, if you set Microsoft Dynamics NAV to send new to-dos automatically, you only need to run the batch job once to populate the Mobile Sales Activity table.

For more information about to-dos, see Creating To-dos.

Mobile Sales extends campaigns with the concepts of selling-in periods and visible dates. If your company has set up campaigns, you can inform salespeople when a campaign can be promoted by specifying the selling-in period for the campaign. For more information, see How to: Add a Selling-in Period to a Campaign in Microsoft Dynamics NAV Classic. For more information about campaigns, see Campaign Table.

Microsoft Dynamics NAV calculates prices on sales orders by including discounts and campaigns. On a mobile device, these complex calculations consume too much memory, so the prices that Mobile Sales displays on the mobile device are pushed to the device from the server. In Microsoft Dynamics NAV, Mobile Sales requires that you run the Mobile Create Customer Price batch job to calculate the price per item per customer and populate this data to a table. You then set the Mobile Sales staging database to synchronize the data to the mobile device where Mobile Sales shows the calculated price when the user is creating a sales order for a customer.

The Mobile Create Customer Price batch job calculates a price per item per customer at the time of execution. The calculation includes the following information:

• Sales prices as defined for a specified customer, all customers, a specified customer price group, or a campaign.

• Line discounts as defined for a specified customer, all customers, a specified customer price group, or a campaign.

If two prices are defined for the same customer on the same item, the batch job applies the lowest price. The Mobile Create Customer Price batch job does not apply the following information:

• Quantity discounts on quantities that are larger than 1.

• Prices and line discounts where the starting date is later than the date and time of running the batch job.

• Expired prices and line discounts.

You can set up a job queue entry that runs the Mobile Create Customer Price batch job according to a schedule that you define. For more information, see How to: Update Customer Item Prices for Mobile Sales in Microsoft Dynamics NAV Classic, and How to: Schedule Jobs for Mobile Functionality in Microsoft Dynamics NAV Classic.

When a salesperson is creating a sales order using Mobile Sales, the customer can sign the sales order on the mobile device to confirm the order. The signature is saved to a separate table when the mobile device synchronizes with the server. By default, the signature is not available from the Sales Order window in Microsoft Dynamics NAV, because prices may have changed between the customer signing the order and the mobile device synchronizing with the server. However, if your setup ensures that the prices on the mobile device are correct, you can enable signatures on sales orders. For more information, see How to: Enable Signatures on Sales Orders in Microsoft Dynamics NAV Classic.

Mobile devices send data and requests back to the server as XML documents, called request documents. Inside Microsoft Dynamics NAV, application objects called document handlers and document types complete the integration. Microsoft Dynamics NAV includes document handlers in a processing codeunit, and four document types that are supported by XML schemas.

A document type manages user access and validation for incoming request documents. The Mobile Sales document types in Microsoft Dynamics NAV handle requests to create sales orders and to create, modify, and delete to-dos and activities.

For more information, see Document Handling for Mobile Sales and How to: Set Up Mobile Document Types in Microsoft Dynamics NAV Classic.