HubDB Foreign IDs: Unlocking Data Beyond Name and ID in HubSpot

HubDB is a powerful tool within HubSpot for managing structured content. It allows you to create dynamic website content, power templates, and build custom applications. However, sometimes working with HubDB, especially with foreign IDs, can present challenges. Let's dive into a common issue and explore solutions based on a recent HubSpot Community discussion.

The Problem: Limited Data from Foreign IDs

Imagine you're building a custom module in HubSpot and using a HubDB table to store information about different services. You've set up a foreign ID column to link these services to another HubDB table containing detailed information like descriptions and images. But when you try to display this information on your website, you're only able to access the name and ID of the linked items. The other data, like the image URL or description, stubbornly refuses to appear.

This was the exact problem faced by a community member. They were pulling data from a HubDB table where a column, 'overview_items', was supposed to retrieve name, image, and descriptive text from a related table. However, only the name and ID were being displayed.

Understanding the Code and Potential Issues

The original poster shared their code snippet, which looked something like this:

{% set column = module.landing_pages.columns %}
{% set title = column.landing_page_title %}
{% set lp = hubdb_table_row(module.landing_pages.table_id, module.landing_pages.id) %}

{% if title %}
{{ title }}
{% endif %}

{% if lp.overview_items %}
  

    {# Loop through each related row from the foreign table. #}
    {% for foreignTable in lp.overview_items %}
      

        {# 'hs_id' and 'name' are standard HubDB row properties. #}
        {{ foreignTable.hs_id }} — {{ foreignTable.name }} — {{ foreignTable.image.url }} — {{ foreignTable.test }}

      
    {% endfor %}
  
{% endif %}

Several community members offered helpful suggestions. One pointed out the importance of ensuring that the data in the referenced table is published and not in draft mode. This is a common oversight that can prevent data from being displayed correctly.

Another suggestion highlighted the need to explicitly read the rows from the foreign table to extract the data. If you have a table-to-table relationship, you must retrieve the table ID and then read the rows explicitly to access the associated data.

The Solution: Accessing Data from a Selected Row

The original poster clarified that they were using a HubDB row select field in a custom module, allowing content creators to select a single row from the parent DB. They wanted to display information from the 'overview_items' column of the selected row, which contained data from a foreign DB.

The key was to modify the code to fetch data from the selected row rather than looping through the entire parent database. Here's how they achieved it:

{% if module.lp_select %}
 
    {% set row = hubdb_table_row(module.lp_select.table_id, module.lp_select.id) %}

    {% if row %}
        

           
{{ row.landing_page_title }}
             
          {% for info in row.overview_items %}
          
{{ info.name }}
          {{ info.description }}
          
          {% endfor %}
        
    {% else %}
        
No row found for the selected ID.
    {% endif %}
{% else %}
    
Please select a row in the module settings.
{% endif %}

This code first checks if a row has been selected in the module settings. If so, it fetches the selected row using hubdb_table_row and then loops through the 'overview_items' column to display the name, description, and image from the foreign DB.

Addressing Warnings

While the code worked, HubSpot was still showing warnings. These warnings often indicate potential issues with data types or undefined variables. Reviewing the specific warnings in the HubSpot interface and ensuring that all variables are properly defined and that the data types match what's expected can help resolve these warnings.

ESHOPMAN Team Comment

This HubSpot Community thread highlights a common challenge when working with HubDB and foreign IDs. The solutions provided demonstrate the importance of understanding how data is structured and accessed within HubDB. For e-commerce businesses using HubSpot, mastering HubDB can unlock powerful capabilities for creating dynamic product catalogs, personalized content, and seamless customer experiences. Don't underestimate the power of explicit data fetching!

By carefully reviewing the code, checking for common mistakes like unpublished data, and explicitly fetching data from related tables, you can overcome these challenges and unlock the full potential of HubDB.