---
title: No Record Linking Applied Button Disabled Use Cases
slug: no-record-linking-applied-button-disabled-use-cases
docTags: 
createdAt: 2025-08-11T11:13:49.000Z
---

## Scenarios

Max is a Turbine orchestrator (Level 2 or 3) and wants his playbook to parse URL output results from the VirusTotal connector to a record Incident application. He wants to use Turbine's application record integration to link records through playbook outputs.

For this use case, there are two issues that could keep Max from successfully linking records. Let's see what happens when Max runs across both issues when the **No record linking applied** button is disabled and how to resolve them before successfully linking records.

First, he creates a playbook and names it **Linking Records**.

:::hint{type="info"}
 This playbook name is for the sake of the use case example. You can name the playbook according to whatever outcome/action you are trying to create.
:::

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/ggI8VWmZGUmw098NDobXq_linking-record-playbook.png" size="80" width="1521" height="452" darkWidth="800" darkHeight="237" position="center" showCaption="false"}

### Use Case 1

**Issue:** The **No record linking applied** button is disabled

**Cause:** There is no record event/record action trigger

Max has created the Linking Records playbook and is now ready to link App A to the playbook via playbook outputs.

1. In the Linking Records playbook, click **Playbook Outputs**.
2. On Playbook Outputs, click the **Application Mapping** tab.
   If Max has not promoted any playbook outputs, he sees the **There are no mappings yet** message.
3. To map the promoted playbook outputs to an application, click **Select Existing Application**.
4. On Select an Application, click the application to which you want to map the playbook outputs, and then click **Confirm**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/5DzzZrQAzd30esB_CcI7i_select-an-application-record-linking.png" size="42" width="500" height="400" darkWidth="800" darkHeight="640" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
From Playbook Outputs, the **No record linking applied** button is *disabled*.
:::

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/NkiYLP4CrrEoROqpN3e-7_no-record-linking-button-disabled.png" size="32" width="180" height="31" position="center" indent="2" showCaption="false"}

5. Hover over the **No record linking applied** button.
   Max sees the **Playbook does not have a record event/record action trigger** tooltip.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/5jEO5rCYfIyiUCdHt508t_playbook-no-record-event-output-mapping.png" size="68" width="1097" height="411" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
Oh no! Max needs to resolve this issue by enabling record linking. To do this, he closes the window and returns to the playbook to add a record event trigger.
:::

6. From the **Application** drop-down, select the application whose records should trigger the playbook (App B in this example) and to which created/updated records in the mapped application(s) (only App A in this example) should be linked.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/oHUimqUIVlVaB30RevXZC_remediate-select-trigger-app-b.png" size="80" width="1600" height="393" position="center" indent="2" showCaption="false"}

2. Click **Playbook Outputs**.
3. On Playbook Outputs, click the **Application Mapping** tab.
   Because Max has added the record event trigger, he now has the ability to select which application to map to the promoted playbook outputs.
4. To map the promoted playbook outputs to an application, click **Select Existing Application**.
5. On Select an Application, click the application to which you want to map the playbook outputs and then click **Confirm**.
   Max selects App A.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/5DzzZrQAzd30esB_CcI7i_select-an-application-record-linking.png" size="56" width="500" height="400" darkWidth="800" darkHeight="640" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
From Playbook Outputs, the **No record linking applied** button is *enabled*.
:::

## Conclusion

Max successfully enabled the record linking button. Now, he needs to link the records. To do this, he navigates to [Linking Records use case](#).

***

### Use Case 2

**Issue:** The **No recording linking applied** button is disabled

**Cause:** The triggering application does not have a reference field for the application to which the playbook outputs are being mapped

Max created the Linking Records playbook. Ready to link App A to the playbook via playbook outputs. He's verified that he already has a record event trigger. He's already mapped App A to the playbook outputs, just like Use Case 1. However, the **No record linking applied** button is still disabled.

Let's see why and how to resolve it!

Max selects App A.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/5DzzZrQAzd30esB_CcI7i_select-an-application-record-linking.png" size="44" width="500" height="400" darkWidth="800" darkHeight="640" position="center" showCaption="false"}

From Playbook Outputs, the **No record linking applied** button is *disabled*.

1. Hover over the **No record linking applied** button.
   Max sees the **No applications exist that have reference fields linked to the App A application** tooltip.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/bZIG5ViQQ1jU_NGK64H0h_no-reference-fields-to-link.png" size="52" width="1091" height="408" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
In this scenario, App B has a reference field; however, it does not reference App A. Therefore, Max cannot link the records in application mapping. Oh no! Max needs to enable record linking by updating the reference fields in the selected application.
:::

2. Navigate to **APPLICATIONS & APPLETS**.
3. Open **App B**.
   Max notices that the FORM LAYOUT section does not contain a Reference field type.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/v8US8F0gqUlt6dUGFKe2s_add-reference-field-type-app-b.png" size="100" isUploading="false" width="800" height="435" darkWidth="800" darkHeight="435" indent="2" showCaption="false"}

4. Click and drag the **Reference** field type to the FORM LAYOUT section.
5. Add a name.
6. In the **Reference Application** drop-down, select **App A**.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/Mcv_OqJ73vBINzLkUTjLc_add-name-add-ref-app-a.png" size="72" width="1624" height="882" darkWidth="800" darkHeight="434" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
Now App B has a reference field type and is mapped to App A.
:::

7. Max navigates back to the playbook.
8. On Playbook Outputs, click the **Application Mapping** tab.
   If Max has not promoted any playbook outputs, he sees the **There are no mappings yet** message.
9. To map the promoted playbook outputs to an application, click **Select Existing Application**.
10. On Select an Application, click the application to which you want to map the playbook outputs and then click **Confirm**.
    Max selects App A.

::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/5DzzZrQAzd30esB_CcI7i_select-an-application-record-linking.png" size="54" width="500" height="400" darkWidth="800" darkHeight="640" position="center" indent="2" showCaption="false"}

:::Paragraph{indent="1"}
From Playbook Outputs, the **No record linking applied** button is now *enabled*.
:::

## Conclusion

Max successfully enabled the record linking button. Now, he needs to link the records. To do this, he navigates to .

:::CtaButton{label="LINKING RECORDS USE CASE" docId="1dFQNymLwaK2_OjVAh2OU" openInNewTab="false"}

:::