Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Orlando Now Platform Capabilities Now Platform capabilities Remote tables

    Remote tables

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Remote tables

    Connect the Now Platform to third-party sources, or to another instance, so that you can retrieve external data and optionally cache it in the memory. You can view external data in lists or forms and process it with standard Glide scripts. You can also group, sort, aggregate, and filter the data just like you would for standard internal tables.

    Remote table components

    Use the following components to build an external data framework:
    Remote tables
    You create remote tables to describe the schema for the data that you want to retrieve from an external source.

    The table definition is in the Now Platform, but its rows, or external records, live in the memory. You create a remote table the same way that you would create a standard internal table. You define columns and controls and designate application access for it just like you would do for an internal table. Unlike an internal table, a remote table does not get its records from the Now Platform database. It gets its records from running an associated script against an external data source.

    To learn more about creating remote tables, see Create a remote table.

    Script definitions
    You create and associate a script definition with a remote table. The external data that you've retrieved using the script can be cached in the memory. You can also designate how this data is cached and how long the data is cached in the memory. Every time that you refresh a list that contains the external data from a remote table, the associated script runs again.

    To learn more about script definitions and how to associate them with a remote table, see Create a script definition for a remote table.

    How remote tables work

    By using a remote table, you can retrieve the data from external sources or from another instance with REST or SOAP services. The external data lives in the memory in read-only mode, which makes the data temporary, or transient, within the Now Platform. You can then view and manipulate the external data without importing or storing it.

    You view the external data in lists or forms in the same way that you view internally stored data. You can manipulate this data by using standard Glide records, business rules, remote APIs, scripting, table reference fields, services, and development tools in the Now Platform.

    Important: All data that is retrieved from the external source lives in the memory, so make sure that your data set is small. To minimize query times, don't add more than 1000 rows to a remote table.

    External data life cycle within the Now Platform

    The data that you retrieve from an external source has a finite duration, or life cycle, within the Now Platform.
    • When you run a script that is associated with a remote table, the retrieved data lives in the memory for as long as the list or form appears. After you close the list or form, that external data is purged from the memory. The next time that you use or view the external data in this remote table, the memory is repopulated from the external system.
    • However, if you have defined caching parameters for the script, the external data remains cached in the memory for the specified caching duration.

      For example, if you designate that the external data should be cached for 300 seconds, it remains cached in the memory for 5 minutes. After that time expires, the cached data is purged from the memory. The next time that you use or view the external data in this remote table, the cache is refreshed from the external system.

    Practical applications for remote tables

    Set up and use remote tables in your enterprise when:

    • You want to fetch external data for temporary use without storing it in the Now Platform. For example, you can create a remote table that fetches weather-related data that appears on a homepage when a user logs in. You would then create an associated script definition that retrieves this data from a third-party weather source that is based on the user's location.
    • You want to retrieve customer details that are stored in an external Customer Relationship Management (CRM) application for viewing in Customer Service Management functions such as Agent Workspace.
      Note: To learn more about data retrieval for Customer Service Management, see Third-party data integration for CSM.
    • You want to retrieve and view personnel data from Human Capital Management (HCM) applications such as Workday or SAP SuccessFactors for use in HR Service Delivery functions.

    Post-filtering and sorting

    When you run a remote table script, it applies post-filtering and sorting query conditions after it adds rows to a table. These applied conditions support any other required queries that the script does not handle. When you apply post-filtering and sorting, the remote table queries work like standard internal table queries.

    When you create remote table scripts, you generally handle the most frequent and expansive queries in the script. Post-filtering queries and sorting can take a long time and may adversely affect how your instance performs. Use a small data set instead so that it doesn't take much time to do post-filtering and sorting.

    Based on your use cases, determine if you should try a narrower query in the external call or a more expansive query. Because the internal filtering and sorting can be expensive to run on large result sets, use a narrower query when the data doesn't require extra filtering. Use a more expansive query when a more general query would return a small result set and would require extra filtering and sorting.

    Differences between remote tables and the IntegrationHub

    Choose whether to use a remote table or IntegrationHub to process external data.
    • When you want to temporarily cache external data for viewing, use remote tables.
    • If you want more advanced importing and transformation options, including Flow Designer, or if you want to develop custom integrations, useß the IntegrationHub.
    Note: If you create a remote table that uses the data from an external source that is outside of the Now Platform, you must have an IntegrationHub subscription entitlement. To learn more about the IntegrationHub, see IntegrationHub.
    • Activate the remote tables plugin

      If you have the admin role, you can activate the Remote Tables plugin (com.glide.script.vtable). This plugin includes demo data and activates related plugins if they are not already active.

    • Create a remote table

      Create a remote table so that you can see the data that you retrieved from an external source.

    • Create a script definition for a remote table

      Define and associate a script with a remote table so that you can retrieve data from an external source with it. The Now Platform retrieves and caches the data for the remote table by running the script against an external data source so you can view or modify it. You can also designate how this external data is cached and how long the data is cached in the memory until the script must run again.

    • Debugging remote table script definitions

      You can enable session debugging for remote table script definitions. To enable script definition logging in a session debug log, set the glide.script.vtable.log.debug property to true.

    • Domain separation and remote tables

      This is an overview of domain separation and remote tables. With domain separation you can separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Remote tables

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Remote tables

      Connect the Now Platform to third-party sources, or to another instance, so that you can retrieve external data and optionally cache it in the memory. You can view external data in lists or forms and process it with standard Glide scripts. You can also group, sort, aggregate, and filter the data just like you would for standard internal tables.

      Remote table components

      Use the following components to build an external data framework:
      Remote tables
      You create remote tables to describe the schema for the data that you want to retrieve from an external source.

      The table definition is in the Now Platform, but its rows, or external records, live in the memory. You create a remote table the same way that you would create a standard internal table. You define columns and controls and designate application access for it just like you would do for an internal table. Unlike an internal table, a remote table does not get its records from the Now Platform database. It gets its records from running an associated script against an external data source.

      To learn more about creating remote tables, see Create a remote table.

      Script definitions
      You create and associate a script definition with a remote table. The external data that you've retrieved using the script can be cached in the memory. You can also designate how this data is cached and how long the data is cached in the memory. Every time that you refresh a list that contains the external data from a remote table, the associated script runs again.

      To learn more about script definitions and how to associate them with a remote table, see Create a script definition for a remote table.

      How remote tables work

      By using a remote table, you can retrieve the data from external sources or from another instance with REST or SOAP services. The external data lives in the memory in read-only mode, which makes the data temporary, or transient, within the Now Platform. You can then view and manipulate the external data without importing or storing it.

      You view the external data in lists or forms in the same way that you view internally stored data. You can manipulate this data by using standard Glide records, business rules, remote APIs, scripting, table reference fields, services, and development tools in the Now Platform.

      Important: All data that is retrieved from the external source lives in the memory, so make sure that your data set is small. To minimize query times, don't add more than 1000 rows to a remote table.

      External data life cycle within the Now Platform

      The data that you retrieve from an external source has a finite duration, or life cycle, within the Now Platform.
      • When you run a script that is associated with a remote table, the retrieved data lives in the memory for as long as the list or form appears. After you close the list or form, that external data is purged from the memory. The next time that you use or view the external data in this remote table, the memory is repopulated from the external system.
      • However, if you have defined caching parameters for the script, the external data remains cached in the memory for the specified caching duration.

        For example, if you designate that the external data should be cached for 300 seconds, it remains cached in the memory for 5 minutes. After that time expires, the cached data is purged from the memory. The next time that you use or view the external data in this remote table, the cache is refreshed from the external system.

      Practical applications for remote tables

      Set up and use remote tables in your enterprise when:

      • You want to fetch external data for temporary use without storing it in the Now Platform. For example, you can create a remote table that fetches weather-related data that appears on a homepage when a user logs in. You would then create an associated script definition that retrieves this data from a third-party weather source that is based on the user's location.
      • You want to retrieve customer details that are stored in an external Customer Relationship Management (CRM) application for viewing in Customer Service Management functions such as Agent Workspace.
        Note: To learn more about data retrieval for Customer Service Management, see Third-party data integration for CSM.
      • You want to retrieve and view personnel data from Human Capital Management (HCM) applications such as Workday or SAP SuccessFactors for use in HR Service Delivery functions.

      Post-filtering and sorting

      When you run a remote table script, it applies post-filtering and sorting query conditions after it adds rows to a table. These applied conditions support any other required queries that the script does not handle. When you apply post-filtering and sorting, the remote table queries work like standard internal table queries.

      When you create remote table scripts, you generally handle the most frequent and expansive queries in the script. Post-filtering queries and sorting can take a long time and may adversely affect how your instance performs. Use a small data set instead so that it doesn't take much time to do post-filtering and sorting.

      Based on your use cases, determine if you should try a narrower query in the external call or a more expansive query. Because the internal filtering and sorting can be expensive to run on large result sets, use a narrower query when the data doesn't require extra filtering. Use a more expansive query when a more general query would return a small result set and would require extra filtering and sorting.

      Differences between remote tables and the IntegrationHub

      Choose whether to use a remote table or IntegrationHub to process external data.
      • When you want to temporarily cache external data for viewing, use remote tables.
      • If you want more advanced importing and transformation options, including Flow Designer, or if you want to develop custom integrations, useß the IntegrationHub.
      Note: If you create a remote table that uses the data from an external source that is outside of the Now Platform, you must have an IntegrationHub subscription entitlement. To learn more about the IntegrationHub, see IntegrationHub.
      • Activate the remote tables plugin

        If you have the admin role, you can activate the Remote Tables plugin (com.glide.script.vtable). This plugin includes demo data and activates related plugins if they are not already active.

      • Create a remote table

        Create a remote table so that you can see the data that you retrieved from an external source.

      • Create a script definition for a remote table

        Define and associate a script with a remote table so that you can retrieve data from an external source with it. The Now Platform retrieves and caches the data for the remote table by running the script against an external data source so you can view or modify it. You can also designate how this external data is cached and how long the data is cached in the memory until the script must run again.

      • Debugging remote table script definitions

        You can enable session debugging for remote table script definitions. To enable script definition logging in a session debug log, set the glide.script.vtable.log.debug property to true.

      • Domain separation and remote tables

        This is an overview of domain separation and remote tables. With domain separation you can separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login