---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Data sources

# Data sources {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A data source is a loading mechanism that maps UI elements to specific database fields using element identifiers. Use data sources to retrieve and display data onto input form screens.

## Concept {#data-sources__section_j35_ysc_p2c}

Data sources enable the mapping of various types of data, such as input values, input actions, and descriptive elements to UI elements on the screen. This mapping is achieved by querying and filtering data from specific tables and fields in the database, and then associating the data with the corresponding UI elements. The mechanism uses an identifier to connect a UI element to a specific data field within a record. This mapping enables the UI element to retrieve and display the specified data.  
Note:  
Data sources aren't supported in offline.

## Data source variables {#data-sources__section_r5g_btc_p2c}

The data source script that maps data into UI elements uses the <var class="keyword varname">DataSourceId</var> and <var class="keyword varname">ElementIdentifier</var> variables.

DataSourceId
:   This variable is the unique identifier for the data source that you're working with. You define it to point to the specific data source you're interacting with in your script.

ElementIdentifier
:   This variable is a unique identifier for each UI element. It helps you specify which UI element a particular piece of data should be mapped to.  
    Note:  
    The <var class="keyword varname">ElementIdentifier</var> variable is listed as <var class="keyword varname">valuesMapper.addRecordMapping</var> in the data source script.

## Data source loading mechanism example usage {#data-sources__section_r2w_ltc_p2c}

Descriptive elements
:   These are elements that provide additional information or context, such as pictures or texts that relate to an input or sections. Configuring a data source is required for descriptive elements because it links UI elements to
    specific fields in a table. This mapping verifies that the data displayed in the UI corresponds to data in the table being iterated by the data source. For more information, see [Configure descriptive elements for input form screens](https://servicenow-prod.fluidtopics.net/FFbWZUPNt_xVm3TNP9iyAQ "Add descriptive elements, such as an image, simple text, rich text, or a mobile card, before an input field within an input form screen. This additional on-screen information provides a context to your users, enabling them to better understand what is required as they enter data into an input form.").

Input actions
:   These are actions that are associated with input fields. Input actions include the addition of a comment, attachment, or navigation buttons. For more information, see [Configure input form actions in an input form screen](https://servicenow-prod.fluidtopics.net/_HUwhK0zZ65JBB6VrSIWyw "Add a button next to input form fields to give users the ability to perform various input actions. These actions include adding a comment, adding one or more attachments, and navigating to other screens.").

Input form actions and refresh option
:   This action enables you to save current data and concurrently make it available to others. This updated data is available when a user either opens the input form or saves their changes. This displayed data includes input
    values, comments, and attachments added by other users. For more information, see [Configure input form screen actions](https://servicenow-prod.fluidtopics.net/b9KFv8LqhN13vsaf1T9MAw "Learn how to configure actions that affect the whole input form screen. These actions can be accessed with an icon or within a more menu button, located in the top menu bar. For example, you can configure a writeback action to save your work progress on the input form.").