> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/setup-and-configuration/mobile-app-setup.md).

# Setup Mobile App

{% hint style="warning" %}
**Note the App below is deprecated and replaced by** [**this solution**](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/mobile-role-center.md)**.** Business Central 19 is **LAST** version where the following is supported.
{% endhint %}

## For all JobManager version *(see below for additional steps regarding older versions)* <a href="#for-all-jobmanager-version-see-below-for-additional-steps-regarding-older-versions" id="for-all-jobmanager-version-see-below-for-additional-steps-regarding-older-versions"></a>

1. Activate the *JobManager* **SOAP** Web Services *6182750 JobManWebService* within the NAV/BC page *Web Service*.
2. Open *Dynamics NAV Administration* on the NAV Server and change the following values:
   1. Tick **Enable SOAP Services**.
   2. **Max Message Size** under **SOAP Services** should be set to minimum *20480*.
3. The port for **SOAP Services** should set up in the firewall with forward to the NAV Server. *On request we can disclose the IP-address of the APP Server.*
4. Check the **SOAP** connection from a browser on another computer (if SSL change http to http**s**):
   * Syntax: `http://MyPublicIP:MySoapPort/MyNavService/WS/MyNavCompany/services`
   * Sample without company: `http://navdemo9999.cloudapp.net:7047/NAV/WS/services`
   * Sample with company: `http://navdemo9999.cloudapp.net:7047/NAV/WS/Cronus%20Danmark%20A%2fS/services`
   * Sample with Tenant: `http://navdemo9999.cloudapp.net:7047/NAV/WS/services?Tenant=Ten999`
   * Result: Should be able to login and see list of services.
5. The following information should be used to setup the APP. Setup the APP can be done at [this site](https://jmgapp.dk/Account/Login.aspx).
   1. Information about the customer.
   2. Information about the NAV partner.
   3. The NAV Servers **public IP-address**. This must be a **fixed IP-addresses**.
   4. The name of the NAV *Instance*.
   5. The name of the NAV *Company* - **Remarks regarding&#x20;*****Company*****:**
      * The name *should* be *without* space and special characters
      * The name *should* only contain these letters *a..z, A..Z og 0..9*
      * The name *CAN'T* contain local letters (eg. danish, german letters) or other regional special letters
   6. Optionally the name of the NAV *Tenant*.
   7. The port for **SOAP Services**.
   8. Domain, User name and password for a valid NAV user.
      * The User must have *JOBMAN-ADMINISTRATOR* or *SUPER* permissions.
   9. Perhaps an *Employee Number* for our test of the connection.
6. If you want to upload images from within the app:
   1. Setup the [Path for new links](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-40) on [JobManager setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md).
   2. Enable for relevant lines with [Add links/image](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/comments-setup-6182371.md#field-801) on [Comments setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/comments-setup-6182371.md).

**Setup the APP is be done by the BC/NAV partner at** [**this site**](https://jmgapp.dk/Account/Login.aspx)**. Contact <support@jobmanager.dk> to be created as user and usage instructions.**

## JobManager version 01.25 and older, the following *also applies* <a href="#jobmanager-version-01.25-and-older-the-following-also-applies" id="jobmanager-version-01.25-and-older-the-following-also-applies"></a>

The following must be done for JobManager versions **earlier** than **01.26**

1. Open *Dynamics NAV Administration* on the NAV Server and change the following values:
   1. **Service Default Time Zone** should be set to *Server Time Zone*, and the Servers Time Zone should be the same as the the Companys main location.

## JobManager version 01.16 and older, the following *also applies* <a href="#jobmanager-version-01.16-and-older-the-following-also-applies" id="jobmanager-version-01.16-and-older-the-following-also-applies"></a>

The following must be done for JobManager versions **earlier** than **01.17** - after any upgrade *to* **01.17** the following can be **reversed**:

{% hint style="info" %}
**Note:** If the customer has special code adjustments to their JobManager APP, then these may still depend on **Odata**.
{% endhint %}

1. Activate all *JobManager* **OData** Web Services within the NAV/BC page *Web Service*.
2. Open *Dynamics NAV Administration* on the NAV Server and change the following values:
   1. Tick **Enable OData Services**.
   2. **Max Page Size** under **OData Services** should be set to minimum *9999*.
   3. **Services Language** under **General** should be set to *en-US*.
   4. **Services Option Text Source** / **Services Option Format** under **General** should be set to *OptionCaption*.
3. Add/Edit the following entry to the *CustomSettings.config* file for each relevant instance:
   * `<add key="EnableODataStrictFiltering" value="false"/>`
   * By default, the files are located in either:
     * *C:\Program Files\Microsoft Dynamics NAV\\##\Service\Instances\\\<instancename>*
     * *C:\Program Files\Microsoft Dynamics NAV\\##\Service*.
     * *C:\Program Files\Microsoft Dynamics 365 Business Central\\##\Service\Instances\\\<instancename>*
     * *C:\Program Files\Microsoft Dynamics 365 Business Central\\##\Service*
4. The port for **OData Services** should set up in the firewall with forward to the NAV Server. *On request we can disclose the IP-address of the APP Server.*
5. Check the **OData** connection from a browser on another computer (if SSL change http to http**s**):
   * Syntax: `http://MyPublicIP:MyODataPort/MyNavService/OData`
   * Sample: `http://navdemo9999.cloudapp.net:7048/NAV/OData`
   * Sample with Tenant: `http://navdemo9999.cloudapp.net:7048/NAV/OData?Tenant=Ten999`
   * Result: Should be able to login and see list of services.

## See also

| Topic                                                                                                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------- |
| [Choose device](https://docs.dynalogic.com/birds-jobmanager-product-overview/getting-started/choose-device.md)                            |
| [Mobile Role Center](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/mobile-role-center.md)                       |
| [Mobile Registration Client App](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/mobile-registration-client.md)   |
| [Get started with App](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/mobile-registration-client/first-steps.md) |
| [Q\&A (App)](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-app.md)                |

## Reference

\
\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/setup-and-configuration/mobile-app-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
