--- sourceDocument: Store Version History Release Notes sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/store-release-notes Release : - store ft:locale : - en-US ft:publication_title : - Store Version History Release Notes ft:clusterId : - rnst bundleId : - rnst --- # Foundation Data Sync for Providers release notes # Foundation Data Sync for Providers release notes {#ariaid-title1} Release version: Store Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Version history for the Foundation Data Sync for Providers application on the ServiceNow Store. Important: For details on system requirements and family compatibility, view the application listing on the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website. ## Version history Version 2.4.10 - September 2026 : * Foundation Data Sync for Providers --- v2.4.10 * Fixed: Custom fields from a consumer are now preserved on offering/subscription items after provider acceptance. {#store-rn-telecom-foundation-data-sync-providers__ul_rvc_bxw_lkc} * Service Exchange for Providers --- v2.4.10 * Fixed * Remote Choice Definitions with Account Secure could fail lookups for external integration users. (PRB2054434) * An emoji in the off-boarding message blocked translation when switching languages. (PRB2032117) {#store-rn-telecom-foundation-data-sync-providers__ul_k44_bxw_lkc} * Changed: Provider Task activity stream now defaults to Additional Comments instead of Work Notes. {#store-rn-telecom-foundation-data-sync-providers__ul_snj_bxw_lkc} * Foundation Data Sync --- v2.4.10 * Fixed * Multi-value list fields could truncate when a later batch sent more data than the first. (PRB2068326) * Requesting an offering referencing a table missing on the requester blocked further requests. (PRB2063217) * Initial payload sync could duplicate or skip records if source data changed mid-sync. (PRB2061531) * Batches after the first could stop processing during bulk sync. (PRB2068330) * Knowledge article attachment sync now correctly handles tables that extend a base table. {#store-rn-telecom-foundation-data-sync-providers__ul_hpw_bxw_lkc} * Changed: Synced KB articles now default to including the provider name in the target KB name. {#store-rn-telecom-foundation-data-sync-providers__ul_wvs_bxw_lkc} * Service Exchange Base --- v2.4.10 * Fixed * Near-simultaneous updates on provider and consumer could drop one side's change. (PRB2029744) * output.ignore=true on a transform didn't actually exclude the field from the sync payload. (PRB2066768) * The Case table lacked a proper label/plural, showing an auto-generated name to some users. (PRB1923483) * A multi-row variable set on a record producer overwrote all rows with the last row's value. (PRB2061638) {#store-rn-telecom-foundation-data-sync-providers__ul_m5k_cxw_lkc} * Changed: Restart Connection after a clone/upgrade now also reactivates capture definitions automatically. * New: Added a scheduled sweep to reactivate capture definitions left inactive after a clone/upgrade. {#store-rn-telecom-foundation-data-sync-providers__ul_evf_cxw_lkc} * Service Exchange Remote Process Sync Transport --- v2.4.10 * Fixed * Onboarding could time out on slow connections, leaving OAuth credentials empty. (PRB2064896) * OAuth credentials during onboarding were sent via URL query params instead of the request body. (PRB2060125) {#store-rn-telecom-foundation-data-sync-providers__ul_lkv_cxw_lkc} {#store-rn-telecom-foundation-data-sync-providers__ul_qkr_cxw_lkc} * Transporter --- v2.4.10: No functional changes. * Service Exchange Health --- v2.4.10 * Fixed * Integration-user-naming scan check didn't validate the required prefix. (PRB2023585) * Some pre-onboarding scan failures didn't generate an Issue record, hiding the block reason. (PRB2025384) * Tightened ACLs on Health records; removed a console log exposing connection data. (PRB2071380) * Fixed message alignment and a duplicate message on the admin-group scan check. (PRB2067053) * Connection Dashboard now shows accurate inbound/outbound transport queue backlog counts. {#store-rn-telecom-foundation-data-sync-providers__ul_twp_1xw_lkc} * Changed: Consolidated two magic-link scan checks into one, gated on whether magic links are enabled. * New * Added a clearer down-connection warning about data loss after 7+ days. * Added a notification to admins when the Admin group has no users. * Added warning messages for missing roles (itil, cmdb_read, personalize, import_admin). {#store-rn-telecom-foundation-data-sync-providers__ul_tzl_1xw_lkc} {#store-rn-telecom-foundation-data-sync-providers__ul_sdv_1xw_lkc} {#store-rn-telecom-foundation-data-sync-providers__ul_ny3_www_lkc} Version 2.2.25 - August 2026 (Australia) : Security enhancements applied. Version 2.3.29 - August 2026 : * Fixed a security issue where a Foundation Data Sync manager could delete, archive, or modify another company's offering, subscription, or CMDB records. (PRB2028446) * Fixed a security issue where a specially crafted company name or field label could execute a malicious script when displayed in a Foundation Data Sync error message. (PRB2028450) {#store-rn-telecom-foundation-data-sync-providers__ul_ol2_kmv_bkc} Version 2.3.18 - June 2026 : * Improved capabilities: * Improve your connection experience, by syncing Knowledge Base articles between provider and consumer instances. * Reduce data inconsistencies by maintaining sys IDs for CMDB data and dependent relationships through transform maps. * Ensure CI functionality is preserved on the destination instance by choosing to automatically create CI dependency relationships when relationship data is received from the source. * Improved compliance through restricted data sync from non production instances to production instances for CMDB tables. Version 2.3.15 - May 2026 : * Fixed: * Inbound Transform Execution * Resolved an issue where inbound transforms could fail to execute due to permission-related constraints, ensuring reliable data ingestion and processing. {#store-rn-telecom-foundation-data-sync-providers__ul_wzg_cqc_cjc} * Connection Entitlements Retention * Fixed a condition where entitlements could be lost after a connection was interrupted and later re-established. Entitlements are now consistently preserved across reconnections. {#store-rn-telecom-foundation-data-sync-providers__ul_xzg_cqc_cjc} * Improved Onboarding Error Handling * Enhanced onboarding behavior so that, if an error occurs in an onboarding flow, a clear error message is presented instead of the process remaining in a "Work in Progress" state. {#store-rn-telecom-foundation-data-sync-providers__ul_yzg_cqc_cjc} {#store-rn-telecom-foundation-data-sync-providers__ul_mzg_cqc_cjc} Version 2.2.13 - April 2026 (Australia) : * New: * Added translations * Change name from Service Bridge to Service Exchange {#store-rn-telecom-foundation-data-sync-providers__ul_udg_pn4_53c} Version 2.3.12 - March 2026 : * New: * Service Exchange Center * Introduced the unified Health Dashboard for improved visibility into connections through a new Heartbeat capability, more accurate connection status, enhanced search and filtering, and centralized issue tracking with validation and resolution. {#store-rn-telecom-foundation-data-sync-providers__ul_bly_wdm_m3c} * Automated Onboarding * Delivered automated Consumer\–Provider onboarding with secure registration, automated pre‑ and post‑onboarding suite validations, improved retry and timeout handling including one‑sided consumer offboarding, and clearer onboarding states with actionable error messaging and recovery. {#store-rn-telecom-foundation-data-sync-providers__ul_cly_wdm_m3c} * Service Exchange Core * Improved transport reliability, strengthened Remote Task error handling, enabled provider‑to‑consumer task variable updates, and ensured Remote Choice values remain accurate. {#store-rn-telecom-foundation-data-sync-providers__ul_dly_wdm_m3c} * Foundation Data Sync * Added bi‑directional data sync from Consumer to Provider, improved attachment handling, introduced automated field mapping, and enhanced visibility into offerings, subscriptions, and revisions. {#store-rn-telecom-foundation-data-sync-providers__ul_ely_wdm_m3c} * Documentation * Restructured Service Exchange documentation. {#store-rn-telecom-foundation-data-sync-providers__ul_fly_wdm_m3c} {#store-rn-telecom-foundation-data-sync-providers__ul_tjy_wdm_m3c} * Fixed: * Improved resilience of RPS outbound (PRB1918189) * RPS connection failures caused by malformed attachments (PRB1969541) * Additional comments are not updated as expected (PRB1984220) * Improved retry behavior during onboarding and Offboarding (PRB1925551) * Corrected CI sync behavior after initial payload (PRB1961406) * Improved handling of inbound email attachments (PRB1920319) * Resolved Clone script conflicts (PRB1966599) {#store-rn-telecom-foundation-data-sync-providers__ul_kd3_xdm_m3c} Version 2.2.5 - September 2025 : * Foundation Data Sync (FDS) enables the structured, periodic sharing of data from provider to consumer instances. It ensures that consumers have access to accurate, up-to-date foundational data from providers, supporting better service delivery and operational alignment. * FDS is a data synchronization mechanism that enables a provider instance to share foundational data with consumer instances on a scheduled basis, such as daily, weekly, or monthly. * FDS supports all CMDB tables and the following non-CMDB tables: Asset, User, Group, Location, Company, and Department. {#store-rn-telecom-foundation-data-sync-providers__ul_hsl_yn5_ngc}