---
schema_version: "1"
id: 70a24497f5a3aba5c3b359dc6d36c1cff39aa72b3a777d25770c16c41839e398
title: Preview and Test an Omniscript
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_preview_an_omniscript_8849.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_preview_an_omniscript_8849.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 643b0cf9bec505f50c7202c667e84bb0afed9941690be4843b62ca1f593f0a10
description: View the Omniscript's appearance and functionality by previewing the Omniscript in the Omniscript Designer.
products:
  - Omnistudio
release: "264"
---
# Preview and Test an Omniscript

View the Omniscript's appearance and functionality by previewing the Omniscript in the Omniscript Designer.

1. In your Omniscript, click **Preview**.
2. For additional preview options, select these properties: <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <tbody><tr class="">
            <th style="vertical-align:top;" headers="d53559e40-option" id="d53559e44">Context ID</th>

            <td style="vertical-align:top;" headers="d53559e40-desc d53559e44">
              <p>If your Omniscript doesn’t have a Set Values Action that defines a
                ContextId, to preview the form with test data, enter a record ID.</p>
              <p>Using Set Values Action to set the context ID only works in preview.</p>
              <p>Confirm that a Context Id is defined in your data source. For example, if
                you have an Omnistudio Data Mapper Extract Action that gets account records,
                you must have an Input Parameter whose <strong class="uicontrol">Data Source</strong> is
                <kbd>ContextId</kbd>, and whose <strong class="uicontrol">Filter
                  Value</strong> is the Data Mapper Extract's output name, such as
                <kbd>AccountId</kbd>.
              </p>
            </td>

          </tr>
          <tr class="">
            <th style="vertical-align:top;" headers="d53559e40-option" id="d53559e74">Preview Device</th>

            <td style="vertical-align:top;" headers="d53559e40-desc d53559e74">
              <p>To preview how your Omniscript appears on different devices, select
                <kbd>Mobile</kbd>, <kbd>Tablet</kbd>, or
                <kbd>Desktop</kbd>.
              </p>
              <p dir="ltr">Fields are arranged in a single column on mobile, even if you have
                put them side by side for the desktop version.</p>
            </td>

          </tr>
          <tr class="">
            <th style="vertical-align:top;" headers="d53559e40-option" id="d53559e98">Theme</th>

            <td style="vertical-align:top;" headers="d53559e40-desc d53559e98">Preview your Omniscript with a Lightning or Newport theme.</td>

          </tr>
          <tr class="">
            <th style="vertical-align:top;" headers="d53559e40-option" id="d53559e107">Reset data fields</th>

            <td style="vertical-align:top;" headers="d53559e40-desc d53559e107">To reset data fields in your Omniscript after making changes, click the
              reload icon. </td>

          </tr>
        </tbody></table>
3. In the Debug panel, view the JSON data in the Data JSON.
4. If needed, click the clipboard icon to copy the full JSON.
5. To open the debug console, click **Action Debugger**.
6. Search for an action name in the Search field.
7. To copy a specific node, click the clipboard icon next to the node. For example, copy Remote Options in an Omnistudio Data Mapper Extract Action.
8. If needed, clear the debug console. To repopulate the debug console with new action request and response data, click ![Reload icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/refresh_icon_flexcards_preview.png).
9. To hide the Data JSON and Action Debugger, click **X**.
    
    To display the Data JSON and Action again, click the debug panel button that appears when the panel closes.

If you see the error "Omniscript is either inactive or has not been deployed," the Omniscript is too large. The Lightning web component for an Omniscript can't be larger than 4 MB because of a [payload data limit](https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/controllers_server_actions_call.htm) with Aura components. In the designer on a managed package, download the Omniscript LWC to check its size.

When you preview an Omniscript with a child Omniscript with a custom CSS, the content for the child Omniscript doesn't show the custom styling.