> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/backup-and-archive-in-salesforce/backup-history/adding-backup-history-button-to-objects.md). # Adding Backup History Button to Objects ## ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3f6faa4230b72167926fbc0a31dd17dc7d74581d%2FSummary2-Small-Icon.svg?alt=media) Overview The Backup History button must be added to an object's List View before it is used for the first time. This step is only required once per object. This guide will show you how to complete the process. {% hint style="info" %} To use Backup History with different object types, add a Backup History button to each object's List View. {% endhint %} ## Add Backup History Button {% stepper %} {% step %} ### Open Object in Object Manager 1. Click the **Gear Icon** in the upper right of the window. 2. Click **Setup** from the dropdown menu.
3. Search for **Object Manager** from the left sidebar. 4. Click **Object Manager** in the left sidebar.
5. Search or scroll to find the Object to which you wish to add the Backup History button.
6. Click the **Object** upon locating it.
{% endstep %} {% step %} ### Create Button 1. Click **Buttons, Links, and Actions** from the left sidebar.
2. Click **New Button or Link**.
3. Complete the **Custom Button or Link Edit** form with the following information:
FieldValue
Label Backup History
NameBackup_History
Display TypeList Button
Display Checkboxes (for Multi-Record Selection)Checked
BehaviorDisplay in existing window with sidebar
Content SourceURL
Multi-Line Textbox below fields/lightning/n/FpPkB__Backup_History?c__objectName=${objectApiName}
{% hint style="info" %} In the **Multi-Line Textbox**, replace `${objectApiName}` with the name of the object you're adding the button to. For the **Opportunity** object, the value entered is `/lightning/n/FpPkB__Backup_History?c__objectName=Opportunity`. {% endhint %} 4. Click **Save**.
{% endstep %} {% step %} ### Add Button to List View 1. Click **List View Button Layout** from the left sidebar.
2. Click the **Down Arrow** dropdown menu at the right side of the **List View** layout. 3. Click **Edit**.
4. Select **Backup History** from the **Custom Buttons > Available Buttons** list. 5. Click the **Add Arrow** to move **Backup History** to the **Selected Buttons** list.
6. Click **Save**.
{% endstep %} {% step %} ### View Backup History 1. Go to the Object to which you added the **Backup History** button. 2. The **Backup History** button will now appear with the other List View buttons.
3. Follow the instructions in the article below to learn how to use Backup History. 4. [Viewing Object Backup History](/backup-and-archive/backup-and-archive-in-salesforce/backup-history/viewing-object-backup-history.md) {% endstep %} {% endstepper %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/backup-and-archive/backup-and-archive-in-salesforce/backup-history/adding-backup-history-button-to-objects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.