Skip to main content

Search

Let us guide you!

Create an Offline Mobile Application

Updated on

On a mobile device, two configuration points require particular attention for offline use:

  • The configuration of link views called during navigation
  • The local download of data required by the mobile user

Contents

1. Configuring link views 2. Displaying link fields 3. Downloading data locally 4. Filters based on view values · Offline behaviour · The local database · Full example
Key principle: the mobile device (unlike the web server) must be explicitly granted access to every field where writing will be required, including link-type fields. The web server has full rights and can write to hidden fields. The mobile client does not · it always operates as a client of the web server.
Configuration steps for offline mode
1

Configure link views

Link views must be configured and link-type fields must be set as writable. Without this, the mobile device cannot write to linked fields, even when a connection is available.

Link view configuration Link view - write access
2

Display link fields in Read / Write mode

Set link fields to Read/Write visibility. Conditional visibility can be used to hide the field from the user when needed, while still preserving write access.

Link fields read/write Field visibility configuration
3

Download data locally (autodownload)

The list displayed inside link fields and the view-based filters only work on mobile if the book's data has been downloaded locally. Use the " target="_blank"mobile configuration in the view of the corresponding linked table, via the " target="_blank"autodownload parameter.

Good to know: autodownload triggers the download of view data when the book is opened (provided an internet connection is available). This parameter is required to display the linked view list inside link-type fields when offline.
4

Make link fields visible in all involved views

To use " target="_blank"view-value filters in link-type fields, those fields must be visible to the mobile device in every involved view, including views used as junction tables.

Behaviour without an internet connection
What works · and what does not · in offline mode
  • Writing data works, but formulas, automatic documents, and automations do not: these processes run on the web server.
  • Links and linked table columns are displayed if the data has been downloaded to the mobile device (mobile config: autodownload).
  • When creating a record from a linked table, the link is written automatically if the link column is visible in the view being used. Conditional visibility can hide the field once the reciprocal link has been established.
  • View filters work if the mobile device has access to the data (autodownload) and all link-type fields are visible in the views involved.
  • Data in Selection and Conditional selection columns (list from another table) is downloaded automatically, without requiring autodownload.
  • The Conditional text field type is an automation: this feature is unavailable in offline mode.
  • Formulas are not calculated in offline mode. Review formula default values for cases where data is absent · this must be configured on the web.
  • A temporary auto-number is assigned based on the data downloaded to the mobile device, then updated once the server syncs. Displaying or relying on auto-numbers in offline mode is not recommended.
  • Field default parameters work normally (today's date, user id).
  • Data created on the mobile device in cache (pending upload to the server) is not included in data downloaded via autodownload. Example: a customer created in the local database will not appear in the link field list until synchronisation with the server has completed.
The local database

When you swipe down on the "Tables" screen, an icon indicates that the mobile device is downloading data from the server.

When an internet connection is active, data entered on the mobile device is automatically written to the server (mobile message: "Saving your data · Everything is synchronised").

TimeTonic mobile local database

Example

Mobile user journey

Here is a concrete order management scenario in offline mode:

  1. I open the record of an existing customer (View: "Customer – Mobile Entry")
  2. I create the order (View: "Order · Mobile Entry")
  3. I create the order lines containing the products and quantities ordered

Link views must be configured and shared within the workspace (they can optionally be hidden).

When creating an order from a customer record, the link and its reciprocal link are written in offline mode as long as the link fields are visible. In the Orders table, conditional visibility on the "Link to Customer" field (visible only when the field is not empty) allows the mobile device to write the link when the line is created, then hide it. Note: once the link has been created and hidden, the mobile device can no longer write to that field or use it for link filters.

Example order link views Example reciprocal link Example full configuration

In the Order Line table, to filter the customer link and display only the customers attached to the order, three conditions must be met:

  • The Order link must be visible in the view used in the Order Lines table
  • The Order link must be visible in the view used in the Customer table
  • Data from the relevant views of the Customer, Order, and Order Lines tables must be downloaded via the autodownload parameter in the mobile configuration

Mobile link filters