Skip to main content
Question

Grabbing associated terms from an attribute in one desktop

  • November 12, 2025
  • 4 replies
  • 47 views
A
Data Pioneer

Hello all,

I am running into an issue when trying to grab terms from attribute items. My current use case is as follows. I have a list of catalog item that are tagged with a term (that we refer to as a jurisdiction) and I am attempting to first find all attributes associated with these catalog items and then find all terms that are tagged to these attributes. The order is as follows:

Find all catalog items with term → get all attributes associated with catalog items → extract all terms on attributes

My plan looks like this:

 

The issue that I am running into is that these plans take a very long time to run sometimes upwards of 30min to an hour depending on the term. I would like to know if there is a more efficient way to do this (either through graphql or some other components etc) or if I am simply stuck waiting with the current speed of the plan.

 

Best Regards,

Andrew

    4 replies

    Albert de Ruiter
    Rocket Pioneer L1
    Forum|alt.badge.img+4
    • Albert de RuiterRocket Pioneer L1
    • Rocket Pioneer L1
    • 113 replies
    • November 13, 2025

    Hi Andrew,

    The second metadata reader is for the catalog item attributes right? Does it also contain a filter on the parent ID, so of the incoming catalog items of the first reader? So I gues something like $parent.$id = "#catalogItemID#", where catalogItemID would be the value in the Id Column Name in the first reader.

    Kind regards,

    Albert

    ivan.kozlov
    Ataccamer
    Forum|alt.badge.img+3
    • ivan.kozlovAtaccamer
    • Ataccamer
    • 55 replies
    • November 13, 2025

    Hi ​@apejko ,

    I’m not sure what kind of level of detail regarding Catalog Items you need but I think just reading the “attribute” entity and it’s “termInstances” embedded entity might be enough to identify all the terms. You can INNER JOIN these streams on attributeId and you’ll have list of attributes with terms applied to them.
    If you need to narrow down the list of CI’s (which are parents of the attributes) - you can use the parent id filter that Albert suggested and provide the list of id’s for catalog items you’re interested in.
     

    Hope this is useful,
    Ivan

    A
    Data Pioneer
    • apejkoData Pioneer
    • Author
    • Data Pioneer
    • 7 replies
    • November 13, 2025

    Hi Andrew,

    The second metadata reader is for the catalog item attributes right? Does it also contain a filter on the parent ID, so of the incoming catalog items of the first reader? So I gues something like $parent.$id = "#catalogItemID#", where catalogItemID would be the value in the Id Column Name in the first reader.

    Kind regards,

    Albert

    Hi Albert,

    Yes the second catalog item is for attributes, and is filtered accordingly. The first catalog item reader will read the catalog items and output the attribute ids and the second reads these ids to check for term instances on the attributes.

     

    A
    Data Pioneer
    • apejkoData Pioneer
    • Author
    • Data Pioneer
    • 7 replies
    • November 13, 2025

    Hi ​@apejko ,

    I’m not sure what kind of level of detail regarding Catalog Items you need but I think just reading the “attribute” entity and it’s “termInstances” embedded entity might be enough to identify all the terms. You can INNER JOIN these streams on attributeId and you’ll have list of attributes with terms applied to them.
    If you need to narrow down the list of CI’s (which are parents of the attributes) - you can use the parent id filter that Albert suggested and provide the list of id’s for catalog items you’re interested in.
     

    Hope this is useful,
    Ivan

    Thank you Ivan,

     

    I dont believe this will work for my use case as I do not want to read all attributes, but just the specific ones that belong to the jurisdiction of the catalog item. Currently my plan is using the filter but it still runs extremely slowly.


    Community Terms of Use & ConditionsCookie settingsAccessibility statement