--- sourceDocument: Brazil Financial Services Operations sourceDocumentLink: https://www.servicenow.com/docs/r/financial-services-operations Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Financial Services Operations ft:clusterId : - finso bundleId : - finso workflow : - Customer and Industry --- # Remote Data Options for Remote Tables # Remote Data Options for Remote Tables {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Remote Data Options for Remote Tables This content explains three architectural approaches for implementing remote tables in ServiceNow Financial Services Operations (FSO): Full Remote, Hybrid, and Full Local. Each approach defines how customer and account data (such as accounts, insurance policies, and transactions) are stored and accessed---either directly from external systems or persisted locally. Understanding these options helps ServiceNow customers choose the best method based on their needs for data freshness, security, and reporting. Show full answer Show less ## Full Remote In the Full Remote approach, all account information is stored externally and accessed in real-time within ServiceNow. This is ideal for scenarios requiring the most current data, such as viewing customer records, relating cases, or obtaining a 360-degree customer view. * **Advantages:** Delivers real-time aggregated data across request types; ensures the latest information is always shown; no sensitive or PII data is stored in ServiceNow. * **Disadvantages:** Remote data is unavailable on parent local tables, which can limit functionality; requires extensive updates to forms, scripts, and UI elements to reference remote tables instead of local ones. ## Hybrid The Hybrid approach combines querying external systems with persisting certain header-level or non-sensitive data locally. It supports Customer 360 views but may require batch uploads or API calls to keep data current. * **Advantages:** Stores only essential, stable data locally; leverages FSO field lookup decorators and plugins to reduce development effort; live remote data remains current on the record. * **Disadvantages:** Locally persisted data can become outdated without regular refresh strategies; aggregate views depend on data synchronization; requires planning for data refresh and synchronization. ## Full Local With Full Local, all customer and account data is stored within ServiceNow FSO, suitable for use cases where data does not need to be real-time and prioritizes reporting or dashboarding. * **Advantages:** Provides fast data access; easier to build Customer 360 views; supports reporting needs effectively. * **Disadvantages:** Data can become stale without refresh strategies; users may need to switch between tools to get the latest information; additional measures may be necessary to secure sensitive or PII data. ## Practical Considerations for ServiceNow Customers * Choose Full Remote if real-time accuracy and minimizing sensitive data storage in ServiceNow are top priorities. * Consider Hybrid for a balance between local data persistence and live data access, keeping in mind the need for synchronization strategies. * Opt for Full Local when data freshness is less critical, and reporting or dashboard performance takes precedence. * Plan updates to forms, scripts, UI components, and data refresh workflows according to the chosen approach to ensure seamless user experience and data integrity. Understand the different approaches of implementing remote tables, and the advantages and disadvantages of each. ## Full Remote {#fso-int_guide-remote-data-options-for-remote-tables__section_xsy_qdj_mcc} In a full remote system, all account information (accounts, insurance policies, and transactions) is stored in an external system. This configuration provides real-time information for customers that want financial accounts/policies to come directly from the source system when: * Looking at a customer record * Relating information to a case * Getting a 360 view of a customer; for example, in the Customer Information tab {#fso-int_guide-remote-data-options-for-remote-tables__ul_jpn_f2j_mcc} {#fso-int_guide-remote-data-options-for-remote-tables__table_mdp_w2j_mcc__entry__2} | Pros | Cons | |-|-| | * Provides a real-time aggregate view of account \& transaction information (Customer 360) for a single customer across multiple request types (for example, Deposit/Loan accounts) * The latest information always appears for fulfillers within the workspace * No sensitive data or Personally Identifiable Information (PII) is stored in the platform {#fso-int_guide-remote-data-options-for-remote-tables__ul_f3q_x2j_mcc} | * No remote table data will be available on parent local tables, resulting in lost functionality with sold product/consumer/account * Updates are required on customer information (C360), record producers, forms, playbooks, reference fields, reference qualifiers, UI actions, scripts, and other areas to point from base system FSO tables to remote tables {#fso-int_guide-remote-data-options-for-remote-tables__ul_iks_bfj_mcc} | [Table 1. Pros and Cons of Full Remote] {#fso-int_guide-remote-data-options-for-remote-tables__table_mdp_w2j_mcc} ## Hybrid {#fso-int_guide-remote-data-options-for-remote-tables__section_dp4_gfj_mcc} In a hybrid system, the system utilizes lookup and save functionality to query information from external systems and persist header-level information into local tables. This functionality can be utilized in tandem with batches/real-time API calls to store certain data locally. Customer 360 is possible in this view, but it may require additional strategies around batch uploads and API calls to populate the data. You must be willing to store certain information about external data in local tables in this configuration. {#fso-int_guide-remote-data-options-for-remote-tables__table_yvz_dgj_mcc__entry__2} | Pros | Cons | |-|-| | * Store only non-sensitive information in the system that is required and doesn't change often * Use the base system FSO field lookup decorator to search \& persist data * The FSO Remote Table plugin can reduce development time if used with lookup and save functionality * Fully remote data that is presented on the record will be current {#fso-int_guide-remote-data-options-for-remote-tables__ul_kdh_2gj_mcc} | * Data persisted onto local tables will become outdated if not refreshed - you must have a strategy to refresh data from the external system * An aggregate view of financial accounts/transactions for an account or consumer won't be shown until information has been persisted (if using lookup and save functionality) or a batch/real-time API synchronization has been performed at runtime {#fso-int_guide-remote-data-options-for-remote-tables__ul_ibh_vgj_mcc} | [Table 2. Pros and Cons of Hybrid] {#fso-int_guide-remote-data-options-for-remote-tables__table_yvz_dgj_mcc} ## Full local {#fso-int_guide-remote-data-options-for-remote-tables__section_zcs_wb4_ncc} In a full local data storage architectural approach, all customer and account information (customer, accounts, insurance policies) is stored in FSO. This configuration provides faster access to information for customers who want financial accounts/policies to be refreshed from the source system on a periodic basis (daily or at regular intervals throughout the day). You may find this approach useful when the use case does not rely on the most recent data and prioritizes reporting needs. This approach helps with the following user actions: * Looking at a customer record * Relating information to a case * Getting a 360 view of a customer; for example, in the Customer Information tab {#fso-int_guide-remote-data-options-for-remote-tables__ul_xs3_cx1_4cc} {#fso-int_guide-remote-data-options-for-remote-tables__table_tvp_2z1_4cc__entry__2} | Pros | Cons | |-|-| | * Best suited for use cases that require less frequently changing information aggregate view * Information loaded into FSO is required for Reporting and dashboarding purposes * Easy to build Customer 360 for a single customer for different personas {#fso-int_guide-remote-data-options-for-remote-tables__ul_yqm_fz1_4cc} | * Data persisted onto local tables will become outdated if not refreshed - you must have a strategy to refresh data from the external system * Users have to manually switch between tools ("swivel chair") for the most updated information * Additional solutions may be needed to secure PII data {#fso-int_guide-remote-data-options-for-remote-tables__ul_ekg_hz1_4cc} | [Table 3. Pros and Cons of Full Local] {#fso-int_guide-remote-data-options-for-remote-tables__table_tvp_2z1_4cc}