> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/salesforce-b2b/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/salesforce-b2b/2.1.0/integrating-the-digital-river-salesforce-b2b-commerce-app/step-2-create-page-labels.md).
# Step 2: Create page labels
You can use CC Page labels to add useful Salesforce B2B Commerce App information such as help text or error messages.
{% hint style="info" %}
Download the **DR\_OrderAPI\_PageLabel-v2\_1\_0.csv** file for this task. It contains the page label information you need to import.
{% endhint %}
{% file src="/files/-MUnghqt9QHrNQvvfgHI" %}
DR\_OrderAPI\_PageLabel\_v2\_1\_0.csv
{% endfile %}
## Step 2a: Install the Data Loader on your local system
You will use the Data Loader to upload the page labels. To install the Data Loader:
1. Click **Setup**  and select **Setup** from the dropdown list.
2. Type `dataloader` in the **Quick Find** field and press **Enter**. \
3. Click **Data Loader**. The Data Loader page appears.
4. Click the appropriate link to download and install the Data Loader for your system.
5. Click the appropriate Installation Instructions link and follow the instructions to install the Data Loader.
## Step 2b: Upload the CC page labels for the Salesforce B2B Commerce App
{% hint style="warning" %}
Install the [Data Loader](/salesforce-b2b/2.1.0/integrating-the-digital-river-salesforce-b2b-commerce-app/step-2-create-page-labels.md#step-8a-install-the-data-loader-on-your-local-system) before you upload the page labels.
{% endhint %}
1. Go to the location where you installed the Data Loader on your local system and double-click **dataloader.bat**. \
2. From the Data Loader app, click **Upsert**. \
3. Select **Password Authentication**.
4. Enter your user credentials for your Salesforce Org, where you need to upload the page labels and click **Log in**. \
5. Choose the **CC Page Label (ccrz\_\_E\_PageLabel\_\_c)** object from the list. 
6. Click **Browse**, locate the **DR\_OrderAPI\_PageLabel.csv** file on your system, and then click **Next**.
7. Select **ccrz\_\_PageLabelId\_\_c** as the external ID field from the dropdown list and click **Next**. \
8. Click **Create Or Edit a Map** to map your fields (CSV columns) to the Salesforce object and click **Next**.\
9. Use the option to **Auto match fields with column** as shown in the following image and click OK:: \
10. Click **Browse**, locate the directory where you want to save success and error files, and then click **Finish**. \
 \
The Data Loader app upserts your records. \
11. Click **View Errors** and check for failures. If there are any failures, correct the problem and try again.
12. Click **OK**.
13. Click **App Launcher**  .
14. Open the **CC Admin** tab, and then click **Indexing**. \
15. Click **Refresh Page Label Cache**. \
 \
You've completed the upsert process for the Digital River B2B CC page labels from the page labels CSV file.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digitalriver.com/salesforce-b2b/2.1.0/integrating-the-digital-river-salesforce-b2b-commerce-app/step-2-create-page-labels.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.