---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# CPQ and Salesforce base package overview

# CPQ and Salesforce base package overview {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

The CPQ and Salesforce base package lets the user use Salesforce Product2 records as configurable products in CPQ, launch the CPQ Admin from Salesforce, and integrate the two applications in other useful ways.
The base package provides the minimum components and configuration for CPQ interacting with Salesforce. This package allows the user to:

* Enable Salesforce Product2 records to be a CPQ configurable product through custom fields added to the Product2 record. For detailed steps, see [Configurable products](https://servicenow-prod.fluidtopics.net/ya9QG84uWw1QYFCZ31KiRw "Learn how configurable products connect blueprints to end-user configuration experiences in CPQ, supporting both headless and Salesforce-integrated use cases.").
* Launch the CPQ Admin from Salesforce, from enabled Product2 records
* Embed the CPQ configuration UI in other Salesforce pages or applications outside CPQ using Visualforce. See [Use case: Embed CPQ UI in a Salesforce VisualForce page](https://servicenow-prod.fluidtopics.net/9zSxKBjEymNAYrwNVkTo0w "Learn how to embed the CPQ user interface in a Salesforce VisualForce page.").
* Access CPQ admin APIs using Salesforce tokens. For detailed steps, see [Admin APIs: Authentication using a Salesforce-connected app](https://servicenow-prod.fluidtopics.net/qVra4ZpNI2LwQtTRXT89Gg "We recommend that you use admin API keys to authenticate admin API calls. An older method is documented here.").
{#logik_io-salesforce_base_package_overview__ul_ccs_hkl_fhc}

## Product2 integration {#logik_io-salesforce_base_package_overview__section_jpr_1ll_fhc}

The base package includes the Logik Enabled checkbox and a link View CPQ Setup that will be populated with a link to the CPQ Admin page when the Logik Enabled checkbox is checked.

## Configuration line item field mapper {#logik_io-salesforce_base_package_overview__section_vcs_bll_fhc}

A flow is available that checks for user-created custom fields on the configuration line item (LGK_ConfigurationLineItem_c), and compares it to data in the Extended Information and Pricing Information fields on the record. If there
are name matches, write the data from the Extended Information or Pricing Information to the custom fields.

Name comparisons ignore case sensitivity, and the "_c" suffix on field names is optional. For example, both "StartDate" and "startDate_c" in Extended Information or Pricing Information will be considered a match for a Salesforce
field named "StartDate_c". If the map contains the same name both with and without the "_c" suffix, the Salesforce will save the value of the field with the suffix.

If the same field names exist in both Extended Information and Pricing Information, the value in Extended Information is written to the custom field.

## Configuration line items {#logik_io-salesforce_base_package_overview__section_htz_fll_fhc}

LGK__ConfigurationLineItem__c stores the product data (bill of materials) that comes out of a configuration. (See below for a complete list of fields.)

The record stores the unique CPQ configuration ID that ties the data back to a specific CPQ configuration session and can be referenced in other flows or triggers in Salesforce.

Quote line fields can be populated with information from a CPQ configuration using records of this object. For additional information, see the following video: [Populate Quote Line Custom Fields from Logik](https://drive.google.com/file/d/1aojT9Pv0BceH2fLbUtEDmBmesn40YSto/view?usp=share_link)

CPQ writes the configuration line item objects when a CPQ configuration is saved. The setting in CPQ Admin must be enabled.  
Hinweis:  
CPQ writes these records into Salesforce, but does not read them. Any changes made to these records will not affect a CPQ configuration.

## Configuration field data {#logik_io-salesforce_base_package_overview__section_e5f_451_nhc}

LGK__ConfigurationFieldData__c stores the field values set in a configuration and contains the unique CPQ configuration ID. (See below for a complete list of fields.)

Creates records for every field from a configuration, even if it has a blank or null value.

Writes the configuration Field Data objects when a CPQ configuration is saved. The setting in CPQ Admin also needs to be enabled.  
Hinweis:  
CPQ writes these records into Salesforce, but does not read them. Any changes made to these records will not affect a CPQ configuration.

## Configuration tenant {#logik_io-salesforce_base_package_overview__section_ysb_x51_nhc}

LGK__ConfigurationTenant__c controls aspects of the CPQ integration with Salesforce.

A single record for org-wide defaults should be created and populated with the Administration URL and Runtime Configuration URL values of your CPQ instance.

For security reasons, the Runtime Client Token field is deprecated. The Skip CPQ Post Install Script checkbox disables product updates that run while installing CPQ's CPQ extension package.