---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Refreshing a ServiceNow CPQ connected Salesforce org

# Refreshing a ServiceNow CPQ connected Salesforce org {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Refreshing a ServiceNow CPQ connected Salesforce org

When you refresh a Salesforce org connected to ServiceNow CPQ, the database sync between the two systems is temporarily disrupted.
This disruption occurs because critical identifiers such as the Salesforce org ID, product IDs, and user names change during the refresh, impacting integrations like Runtime APIs, product sync, and user access configurations.
To restore full functionality, specific steps must be followed after the refresh.
Show full answer Show less  

## Key Actions for ServiceNow Customers

* **Create a support case:** Initiate a case via the ServiceNow Support portal to handle the ServiceNow CPQ side of the refresh. Provide essential details including the ServiceNow CPQ environment URL, refresh date, desired data handling approach (retain or start fresh), new Salesforce org ID (or TBD if unknown), Salesforce My Domain URL if changed, usernames for ServiceNow CPQ Admin access, any hostname changes, and the provisioning username with email and admin privileges.
* **Update Salesforce configuration:** After the refresh, update the Salesforce Custom Settings by navigating to *Salesforce Setup \> Custom Settings \> Manage ServiceNow CPQ tenant* and modify the Runtime Configuration URL and Administration URL accordingly.
* **Adjust Salesforce CPQ settings (if applicable):** If Salesforce CPQ is in use, update the external configurator URL at *Installed Packages \> Configure Salesforce CPQ \> Additional Settings* to point to the new site URL ending with `/ui/configure`.
* **Reset Refresh Token User:** In ServiceNow CPQ Admin settings, delete or reset the Refresh Token Username to align with the new Salesforce org credentials.
* **Recreate Runtime Clients:** If Runtime APIs are employed, create new Runtime Clients in ServiceNow CPQ Admin to restore API functionality.

## Why This Matters

These steps are crucial to reestablish seamless integration and data synchronization between ServiceNow CPQ and the refreshed Salesforce org. Without completing them, key functionalities such as pricing, product data syncing, and administrative access can fail, impacting your CPQ operations.

## Expected Outcomes

* Restored database sync and integration between ServiceNow CPQ and the refreshed Salesforce org.
* Updated configuration reflecting new Salesforce org identifiers and URLs.
* Properly configured admin access and Runtime API clients ensuring uninterrupted CPQ operations.  
Refreshing a Salesforce org severs the database sync between ServiceNow CPQ and Salesforce. To get things working again, take these steps after the refresh.

When a ServiceNow CPQ connected Salesforce org is refreshed, the database sync between ServiceNow CPQ and Salesforce will be temporarily broken. This is because a refresh automatically changes many pieces of the Salesforce org, including the Salesforce org ID, product IDs, and user names.

These ID changes are used for many integration points between the two systems, such as the Refresh Token User Runtime APIs that depend on a User ID, the product, the Pricebook, Pricebook entry sync, and the user access set up for
the ServiceNow CPQ Admin.

To complete the ServiceNow CPQ side of the refresh, create a support case by using the [ServiceNow Support portal](https://support.servicenow.com). For step-by-step instructions, see [Create a case on Now Support for CPQ Customers](https://support.servicenow.com/kb?sys_kb_id=d67d3e71475d7a90f64de825126d4326&id=kb_article_view).

When you submit the support case, provide the following information:

* The current ServiceNow CPQ Environment URL
* The date the refresh will be performed
* What you'd like to do with the connected ServiceNow CPQ environment's existing data:
  * Retain its data (a repoint)
  * Start from scratch (decommission and create a new environment)
  {#refreshing_a_logik_connected_salesforce_org__ul_xxd_kfn_fhc}
* The new SFDC org ID (if unknown at the time, simply give TBD)
* The SFDC My Domain URL (if changed)
* The SFDC Usernames for users that will need ServiceNow CPQ Admin access
* Whether you want to change the ServiceNow CPQ environment host name, and if so, what it should be
* The provisioning username with the email address and system administrator privileges.

{#refreshing_a_logik_connected_salesforce_org__ul_okp_3fn_fhc}  
Once the environment is refreshed, you will need to:

* Send the new SFDC org ID
* Navigate to Salesforce Setup \> Custom Settings \> Manage ServiceNow CPQ tenant and modify the ServiceNow CPQ URLs.

  Navigate to SFDC \> Setup \> Custom Settings \> Manage ServiceNow CPQ Tenant \> Edit, and change the Runtime Configuration URL and Administration URL.
* If using Salesforce CPQ, change the external configurator URL.Navigate to SFDC \> Setup \> Installed Packages \> Configure Salesforce CPQ \> Additional Settings, and change the external configurator URL to the new
  site with `/ui/configure` appended to the end.

* Submit a new refresh token user name with system administrator permissions.Navigate to ServiceNow CPQ Admin \> Settings, and delete or reset Refresh Token Username.

* If using any Runtime APIs in SFDC, create new Runtime Clients.Navigate to ServiceNow CPQ Admin \> Runtime Clients, and create the new clients.

{#refreshing_a_logik_connected_salesforce_org__ul_nsc_pfn_fhc}

